NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #5869 most downloaded on Packagist
Build fast native Android and iOS applications with PHP and PAM.
Latest stable
v1.54.3
Last release today
19 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
386 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
PAM Native 1.46.12 (on top of 1.46.11).
PAM Native 1.46.12 (on top of 1.46.11).
iOS keyboard and pager glide follow-ups, on top of 1.46.11.
contentOffsetAnimationMs no longer snaps a page glidePamOffsetGlideTests.PAM Native 1.46.11 (on top of 1.46.10).
PAM Native 1.46.11 (on top of 1.46.10).
Android gestures and keyboard, list content insets, navigation insets and
encoder memory, on top of 1.46.10.
pressedBackgroundColor paints the pressed state nativelyDrag::follow() takes a proportional factor, so a dragged view canKeyboardProgress (extension property 1009): a native IME driver thatpaddingTop/paddingBottom as nativeYour coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
PAM Native 1.46.10 (on top of 1.46.9).
PAM Native 1.46.10 (on top of 1.46.9).
iOS keyboard, cube pager, media and layout follow-ups to the 1.46.9 iOS port, on top of 1.46.9.
PamMediaRetireTests.fling (UIScrollView keepsisDragging through it) and changes made inside an animation (keyboardanim; with the trace on, PamGlide lines log everycontentOffset request and glide stall (debug builds).PAM Native 1.46.9 (on top of 1.46.8).
PAM Native 1.46.9 (on top of 1.46.8).
iOS port of the Android list, keyboard, media and Pressable guarantees, iOS bubble borders and cube pager glide, Android document paint order and keyboardDismissMode on lists, on top of 1.46.8.
zIndex respected, likeelevation keeps its shadow but no longerPamPaintOrderTest,PamZIndexHostInstrumentedTest.keyboardDismissMode (on-drag / interactive) applies toVirtualizedList, FlatList and SectionList too. On Android a user dragscrollRequest committed during the user's drag or fling is droppedendReached counts thePamListNativeScrollTests.autoPlayVisible / autoPlayGroup (1006/1007) decidedPamVisibleAutoplayTests.contentOffsetAnimationMs: the same target committed again while thePAM_LIST_TRACE=1 (or the PamListTrace user default)PamListTrace.onLongPress lends the longdelayLongPress; the nestedonLongPress keepsPamNestedLongPressTests.<Modal> component, likevisible false or unmounted) flies them home, with the Modal fading inlaunchOnTap() hand-off to a Modal stays Android-only.PamModalSharedTransitionTests.PAM Native 1.46.8 (on top of 1.46.7).
PAM Native 1.46.8 (on top of 1.46.7).
Runtime batch FIFO fix (intermittent "cannot contain children"), nested Pressable long press, RN tail truncation and subpixel styled text on top of 1.46.7.
Node ... cannot contain children). The immediate flush of anonLongPress lends the longdelayLongPress. The nested press is cancelled, so its onPress does notnumberOfLines and the tail ellipsis is cut exactlyPAM Native 1.46.7 (on top of 1.46.6).
PAM Native 1.46.7 (on top of 1.46.6).
Keyboard follow, native visible autoplay (extension props 1006/1007) and list seam fix on top of 1.46.6.
Android keyboard: the root follows every frame of the IME show/hide
animation (engine viewport and layout), so content above the keyboard
moves with it in one motion instead of jumping to the end state; keyboard
visibility observers see a closing keyboard hidden from its first frame and
an opening one once it is up (keyboardWillHide / keyboardDidShow). A list
resting at its end pins its newest row in the same layout pass as a
resize (no one-frame lag). PamKeyboardFollowTest.
Android virtual lists: a cell root without margins fills its slot (a 1 px
seam showed between rows); the cumulative row snap of f9437e1 is
reverted (it moved chat rows 1-2 px against React Native).
PamListPixelSnapTest.
MediaPlayer autoPlayVisible / autoPlayGroup (extension properties 1006
and 1007, MediaPlayer::autoPlayWhenVisible()): Android plays a video while
at least that share of it shows and its list is at rest, one per group and
list, pausing below fraction - 0.2 and releasing the decoder 1.5 s later;
positions resume per source. No PHP round-trip for autoplay changes.
PamAutoplayPolicyTest (JVM), PamVisibleAutoplayInstrumentedTest.
Keyboard follow, native visible autoplay (extension props 1006/1007) and list seam fix on top of 1.46.6.
Android keyboard: the root follows every frame of the IME show/hide animation (engine viewport and layout), so content above the keyboard moves with it in one motion instead of jumping to the end state; keyboard visibility observers see a closing keyboard hidden from its first frame and an opening one once it is up (keyboardWillHide / keyboardDidShow). A list resting at its end pins its newest row in the same layout pass as a resize (no one-frame lag). PamKeyboardFollowTest.
Android virtual lists: a cell root without margins fills its slot (a 1 px seam showed between rows); the cumulative row snap of f9437e1b is reverted (it moved chat rows 1-2 px against React Native). PamListPixelSnapTest.
Android virtual lists snap rows like Yoga: a row spans round(start) .. round(start + extent) of the running offset instead of rounding each height alone (rows drifted 1-2 px and left a 1 px hairline between cells). Kept rows keep their sub-pixel phase, so rows joining above or below never resize the rows shown; a cell root without margins fills its snapped slot. PamListPixelSnapTest.
MediaPlayer autoPlayVisible / autoPlayGroup (extension properties 1006
and 1007, MediaPlayer::autoPlayWhenVisible()): Android plays a video while
at least that share of it shows and its list is at rest, one per group and
list, pausing below fraction - 0.2 and releasing the decoder 1.5 s later;
positions resume per source. No PHP round-trip for autoplay changes.
PamAutoplayPolicyTest (JVM), PamVisibleAutoplayInstrumentedTest.
PAM Native 1.46.6 (on top of 1.46.5).
PAM Native 1.46.6 (on top of 1.46.5).
RN layout/text parity and Android list/media fixes on top of 1.46.5, no protocol change.
Layout: a stretched flex item is bounded by its own min/max cross size
like Yoga, so a max-width child of a column (View or Text) wraps its
text at that width instead of the column's.
Android Input font sizes are whole (ceiled) pixels like React Native's
TextInput (15sp at 2.625 draws at 40 px, not 39.375).
Android text: numberOfLines="1" lays the text out as one unwrapped line
(horizontally scrolling TextView, no input or marquee change), so the tail
ellipsis cuts mid-word like React Native ("hoje à…") instead of breaking
at the last word first and dropping text that fits ("hoje …"). Head and
middle ellipsize modes now work on single lines too.
Android media in scrolling (not paged) lists prepares its player when the
view shows on screen and the list is not flinging, instead of when the row
is bound ahead of the viewport (S23 feed: PSS 389 -> 310 MB, p99 32 -> 23 ms,
janky 3.84% -> 2.57%). Pagers (reels) keep preparing their next page.
Android media: a player lets go of its video surface on its own thread
before the surface (and texture) is released, and its owner thread
outlives the release by 3 s, so a codec still starting never writes into
an abandoned queue (CodecException, "flush() ... at Released state") and
late codec events never hit a dead thread. PamMediaChurnInstrumentedTest.
Android lists: a page landing above the rows on screen (older history)
never moves or rebuilds them: window reports made before the rows changed
are recognized (@first,last,rows) and ignored, a full rebind keeps the
first visible row by id, and the row-index anchor (for placeholder runs)
no longer applies to single rows (it jumped by the rows that joined).
Android: during a fling, windowed lists ask for rows three screens ahead.
windowSize lists follow their rows by key when rows join or leave
before the window (an older page above a conversation): the rows on screen
stay built instead of being released and replaced (a visible swap/jump).
Android: media players run under a manifest-declared media attribution
tag (Samsung logged an AppOps "attributionTag not declared" error per
playback). Debug builds: setprop log.tag.PamCellPerf DEBUG profiles each
list cell bind (create, attach, properties per key, events, layout).
windowSize lists: a row released by the window keeps its native node
(its placeholder takes the row's root kind), so the list keeps its anchor
and pixel position; a list opened with initialScrollIndex past its end
plans its first window around the end.
Android virtual lists: a scroll to a cell anchors on that cell (estimated
placeholder heights above it no longer move the target away); a windowed
list keeps a visible single row in place when rows join above it (the row
index anchor used to jump by those rows).
Navigation focus follows the first mount: a screen opened through
Route::navigate() (or any router entry) now gets
NavigationLifecycleAware::navigationFocused() after setup() and
onMounted(), then its onFocus() hooks, as in Vue/React Navigation.
Previously navigationFocused() ran before the first render, so a focus
handler using something setup() created saw it unset. Blur, back,
kept-alive, modal and tab ordering are unchanged; a screen left before its
first mount gets neither focus nor blur.
Windowed virtual lists opened with initialScrollIndex past the last row
(a conversation opening at its newest message) materialize their last rows
instead of the first 48 (PHP and the Android/iOS native encoder).
Android: a virtual list row re-measured while the list rests keeps the
first fully visible row at its pixel offset (a partly hidden top row that
grew used to push every row on screen).
Android debug builds: adb shell setprop log.tag.PamListTrace DEBUG logs
each drawn frame's visual row motion of virtual lists (dy, rows in common,
scroll state), a recording-free way to prove there are no jumps or snaps.
Virtual lists (Android): a scrollRequest committed while the user's own
drag or fling moves the list is dropped unless the user asked for it (a
press, long press or submit since the gesture began, e.g. send or "jump to
latest"). Anchor-style requests issued while a window shifted cut flings
short and jumped the list; run after the fling they snapped it at rest.
Android: rows prepended right below a leading row on screen (a header, a
"loading older" row) keep the first row after them at its pixel offset,
like any prepend above the viewport (RecyclerView kept the header and
pushed the content down). New docs section "Native scrolling guarantees of
long lists", PHP test list_native_scroll.php, Android
PamListNativeScrollInstrumentedTest and PamHeadInsertAnchorTest.
Android: the per-frame "Received a PHP render frame" log is verbose and
compiled out of release builds (NDEBUG); debug PamNativePerf lines now
show each commit's own kind and sizes (frame=, frameIn=, frameOut=)
next to the engine totals (totalFull=, totalPatch=, totalInBytes=),
which used to read like per-frame values.
Shared elements between a screen and a <Modal> (the component, not a
route), with the same shared tag and no app code: opening the Modal flies
every tag on screen below into it, and closing it (visible false or
unmounted) flies its tags home to the instance they came from. Media reuse
the decoded picture and morph frame, crop and radius; a launchOnTap()
flight is handed to the Modal the tap opened; a view released by
Drag::holdAt(...) flies home from where it was let go. The Modal fades in
step with the flights, an unmounted Modal keeps its window (untouchable)
until they land, and a Modal over a Modal pairs with the one below
(Android; iOS keeps the Modal animation for now).
A shared element flies home to the instance it left from while that
instance is still on screen, even when the last touch was elsewhere (a close
button), and the touch that picks among repeated tags is tracked on screen
coordinates across windows.
PAM Native 1.46.5 (on top of 1.46.4).
PAM Native 1.46.5 (on top of 1.46.4).
Shared element fixes and instant launch on top of 1.46.4, no protocol change.
SharedTransitionStyle::launchOnTap() on a tappedPAM Native 1.46.4 (on top of 1.46.3, which adds real shared elements), no protocol change.
PAM Native 1.46.4 (on top of 1.46.3, which adds real shared elements), no protocol change.
PAM Native 1.46.3 (on top of 1.46.2) adds real shared elements.
PAM Native 1.46.3 (on top of 1.46.2) adds real shared elements.
Real shared elements on top of 1.46.2, no protocol change (core and extension identifiers as in 1.46.2; the shared tag and style use the existing core keys).
shared tag in templatessharedStyle for its motion). Media flights reuse the decoded image orSharedTransitionStyle::returning() sets the curve homeSharedTransitionEasing::EaseIn); springs are physical (damping ratio,Fade only the top route fades, in step with theTransparentModal + Fade route flies on iOS too (customDrag::holdAt(...): a release toward those snaps keeps the view where thenativeRefs on the whole screen whenPAM Native 1.46.2 (on top of 1.46.1) has fixes and one addition. It has no protocol change ( protocol= is the same as 1.46.1) and needs the same plugi
PAM Native 1.46.2 (on top of 1.46.1) has fixes and one addition. It has no protocol change (protocol= is the same as 1.46.1) and needs the same plugins as 1.46.0.
Image::prefetch() accepts packaged asset:// images. Each image is decoded once per process at full resolution, off the UI thread, and kept in memory: at most 8 images or 48 MiB, dropped on a critical memory trim or an iOS memory warning. An Image with that exact source then paints in the frame that binds it, with no decode or fade. A theme switch between two preloaded sources only swaps the bitmap. This works on Android and iOS. Use it for a screen background that must appear in the first frame of a push.contentSize/layoutMeasurement, and the new ScrollPhaseEvent::distanceFromEnd() gives how far the viewport is from the end of the content (Android, iOS).Gates at the release commit (cd1faf9):
run.php and protocol-parity.pycargo test (275), cargo fmt --check and cargo clippy -D warningsbuild-for-testing on Xcode 26.6 for the core and every moved plugin, plus XCTest on an iPhone 17e Simulator: 47/47 (motion, inline image, animated image, layout parity)Assets are built reproducibly, and the package budgets were verified.
Full list: CHANGELOG.md 1.46.2.
Fixes and one addition on top of 1.46.1, no protocol change (core and extension identifiers as in 1.46.1).
Image::prefetch() accepts packaged asset:// images: each is decoded once
per process at full resolution, off the UI thread, and kept (a GPU bitmap on
Android 9+; at most 8 images / 48 MiB, dropped on a critical memory trim or
iOS memory warning). An Image with that exact source then paints in the
frame that binds it, before layout, with no decode, cache-size match or
fade, and a theme switch between two preloaded sources only swaps the
bitmap (Android, iOS). Use it for a screen background that must be there in
the first frame of a push.initialScrollIndex) that the
reader scrolled away from is no longer pulled back to the end when a row
re-measures (an image finished loading), its viewport resizes or rows land;
nothing re-pins a list while it is dragged or flung, and a list scrolled back
to its end follows it again. Previously followEndOnResize treated every
list opened at its end as still resting there, so a long chat timeline
snapped back to the bottom while the reader scrolled up.on:scrollBeginDrag, on:scrollEndDrag,
on:momentumScrollEnd) carry RN's contentSize/layoutMeasurement as
ScrollPhaseEvent::$contentWidth/$contentHeight/$layoutWidth/
$layoutHeight, and ScrollPhaseEvent::distanceFromEnd() tells how far the
viewport is from the content's end (Android, iOS).PAM Native 1.46.1 (on top of 1.46.0) is a fix release. It has no protocol change ( protocol= is the same as 1.46.0) and needs the same plugins as 1.46
PAM Native 1.46.1 (on top of 1.46.0) is a fix release. It has no protocol change (protocol= is the same as 1.46.0) and needs the same plugins as 1.46.0.
Navigator::interceptSystemBack(), such as closing a GIF or emoji panel, changes nothing on screen. One that pops plays its normal transition, like React Navigation with a consuming BackHandler.TapEffect::layer() lets a tap effect animate more than one layer. Each extra pam-motion program plays on the anchor's next child, on Android and iOS.Gates at the release commit (59046fa): PHP SDK run.php, protocol-parity.py, cargo test (275), cargo fmt --check, cargo clippy -D warnings, Kotlin compile with 389 JVM unit tests (326 core, 63 in the moved plugins), and iOS build-for-testing on Xcode 26.6. Assets are built reproducibly, and the package budgets were verified.
Full list: CHANGELOG.md 1.46.1.
Fixes on top of 1.46.0, no protocol change (core and extension identifiers as in 1.46.0).
Navigator::interceptSystemBack() (closing a GIF or emoji panel) changes
nothing on screen instead of flickering the route, and one that pops plays
its normal transition, like React Navigation with a consuming BackHandler.TapEffect::layer(): a tap effect can animate more than one layer. Each
extra program plays on the anchor's next child alongside the first (Android,
iOS; the protocol string carries one pam-motion program per layer).Upgrade. Every moved class keeps its old name in 1.46 as a deprecated alias, but only with its plugin installed; without it, the first use throws Plug…
PAM Native 1.46.0 (on top of 1.45.1) slims the core: optional native capabilities move to plugins. It has no protocol change (protocol= is the same as 1.45.1); the engine changes only for the vertical pager safe area fix (engine=6f129923845fd14c).
Upgrade. Every moved class keeps its old name in 1.46 as a deprecated alias, but only with its plugin installed; without it, the first use throws PluginException naming the package. The aliases go away in 1.47.
Moved API (Pam\Native\…) |
Install |
|---|---|
System\Location, LocationError, LocationPosition, LocationServicesResult |
composer require pushinbr/pam-native-location:^0.1 |
System\Contacts, Contact, System\Sms |
composer require pushinbr/pam-native-contacts:^0.1 |
System\Sensors, SensorReading, SensorType |
composer require pushinbr/pam-native-sensors:^0.1 |
System\AudioRecorder, AudioRecording, AudioRecordingProgress |
composer require pushinbr/pam-native-audio:^0.3 |
System\ImageEditor, ImageCropRatio, ImageFilterType, ImageTextLayerStyle |
composer require pushinbr/pam-native-media-editor:^0.5.1 |
System\MediaLibrary, System\MediaCapture, System\ViewCapture, MediaAsset, MediaAssetPage, MediaAlbum, CapturedImage, CaptureType, ImageCaptureFormat |
composer require pushinbr/pam-native-media:^0.7.1 |
System\Biometrics, BiometricKind, BiometricError |
composer require pushinbr/pam-native-auth:^0.4.1 |
System\Notifications, System\PushNotifications, PushMessage, PushToken, PushProvider, PushEventType, NotificationImportance, Notifications\* |
composer require pushinbr/pam-native-notifications:^0.1.3 |
System\IncomingShares, IncomingShare |
composer require pushinbr/pam-native-share-extension:^0.4.1 |
UI\WebView |
composer require pushinbr/pam-native-webview:^0.1.1 |
Permissions, manifest entries and native dependencies move with them, so an app that does not use a capability no longer builds it in.
WatchChannel and ActivityResultHost. On iOS, PamMediaDiskCache and PamPrivateFilePath are public so plugins can compile as their own Swift module.interceptSystemBack()) settles back instead of sliding the route away; Android 15's Back key closes in-screen UI like React Native.toPixelFromSP; a text with no colour is opaque, so colour emoji are not faded.pagingEnabled list or scroll) is full-bleed, so each page's bottom chrome is no longer clipped.Gates at the release commit (897acc5): PHP SDK run.php, protocol-parity.py, cargo test (CLI, engine, protocol), cargo fmt --check, cargo clippy -D warnings, Kotlin compile with 388 JVM unit tests (325 core, 63 in the moved plugins), and iOS build-for-testing on Xcode 26.6 for the core and every moved plugin with their tests. Assets are built reproducibly, and the package budgets were verified.
Full list: CHANGELOG.md 1.46.0.
Core slimming: optional native capabilities move to plugins, the core keeps the runtime, protocol, renderer/layout, primitives, navigation, state, basic HTTP, gestures/accessibility, storage and the generic hooks plugins need. Includes everything since 1.45.1.
The core no longer ships these APIs. Each old class name still works in
1.46 as a deprecated alias of the plugin class, but only when the plugin is
installed; without it, the first use throws PluginException naming the
package. Add the plugin and switch to the new namespace before 1.47, which
removes the aliases. Plugin versions below are the first ones built for
pushinbr/pam-native ^1.46.
Old core API (Pam\Native\…) |
New class | Install |
|---|---|---|
System\Location, LocationError, LocationPosition, LocationServicesResult |
Pam\Native\Location\* |
composer require pushinbr/pam-native-location:^0.1 |
System\Contacts, Contact, System\Sms |
Pam\Native\Contacts\* |
composer require pushinbr/pam-native-contacts:^0.1 |
System\Sensors, SensorReading, SensorType |
Pam\Native\Sensors\* |
composer require pushinbr/pam-native-sensors:^0.1 |
System\AudioRecorder, AudioRecording, AudioRecordingProgress |
Pam\Native\Audio\* |
composer require pushinbr/pam-native-audio:^0.3 |
System\ImageEditor, ImageCropRatio, ImageFilterType, ImageTextLayerStyle |
Pam\Native\MediaEditor\* |
composer require pushinbr/pam-native-media-editor:^0.5.1 |
System\MediaLibrary, System\MediaCapture, System\ViewCapture, MediaAsset, MediaAssetPage, MediaAlbum, CapturedImage, CaptureType, ImageCaptureFormat |
Pam\Native\Media\* |
composer require pushinbr/pam-native-media:^0.7 |
System\Biometrics, BiometricKind, BiometricError |
Pam\Native\Auth\* (System\Biometrics → Auth\LegacyBiometrics) |
composer require pushinbr/pam-native-auth:^0.4.1 |
System\Notifications, System\PushNotifications, PushMessage, PushToken, PushProvider, PushEventType, NotificationImportance, Notifications\* (ConversationNotification, NotificationAction, NotificationActionType, NotificationCredentials, Person, PushRendering, PushRenderingRule, ActionEndpoint, ReplyFailures) |
Pam\Native\Notifications\* (the Notifications\* value types → Notifications\Contracts\*) |
composer require pushinbr/pam-native-notifications:^0.1.2 |
System\IncomingShares, IncomingShare |
Pam\Native\ShareExtension\* |
composer require pushinbr/pam-native-share-extension:^0.4.1 |
UI\WebView |
Pam\Native\WebView\WebView |
composer require pushinbr/pam-native-webview:^0.1.1 |
NativeOperation::SensorRead (19) and the WebView NodeKind stay
reserved in the protocol and answer a failure that names the plugin.protocol= marker unchanged).Wave two: notifications, incoming shares, biometrics, media library/system
capture/view capture, and WebView move to optional plugins. Deprecated
MovedToPlugin PHP aliases remain until 1.47; suggest lists their packages.
Generic plugin hooks: activity intents/foreground/reload, permission and native-ref hosts, PHP runtime reset/route focus, reserved-node property/event delegation. The WebView NodeKind stays reserved and delegates to its plugin.
iOS keeps push-provider/delegate hooks and photo-URI helpers used by basic Image/MediaPlayer/Files; optional notification presentation leaves the core.
Core slimming (the core keeps only runtime, protocol, renderer/layout, primitives, navigation, state, basic HTTP, gestures/a11y, storage and the generic hooks plugins need). Moved to plugins, each with its native module, permissions and dependencies:
System\Location and LocationError/LocationPosition/
LocationServicesResult → pushinbr/pam-native-location
(Pam\Native\Location\*). Play Services Location and the location
permissions leave the core Android build.System\Contacts, Contact and System\Sms →
pushinbr/pam-native-contacts (Pam\Native\Contacts\*); the
contacts permission leaves the core manifest.System\Sensors, SensorReading, SensorType →
pushinbr/pam-native-sensors (Pam\Native\Sensors\*); the core
NativeOperation::SensorRead (19) stays reserved and answers a failure
that names the plugin.System\AudioRecorder, AudioRecording, AudioRecordingProgress →
pushinbr/pam-native-audio (Pam\Native\Audio\*).System\ImageEditor, ImageCropRatio, ImageFilterType,
ImageTextLayerStyle → the media editor plugin
(Pam\Native\MediaEditor\*).
Migration: every old class name is a deprecated shim for 1.46 only. With
the plugin installed it is an alias of the plugin class (same class, so
instanceof, enum cases and type hints keep working); without it the
autoload throws PluginException with the exact composer require. The
plugins are listed under suggest. The shims are removed in 1.47.Plugin API (generic hooks the moved modules need): WatchChannel
(bounded watch/next/stop channel) moves to the Android plugin API and is
public on iOS; Android ActivityResultHost (implemented by the PAM
activity) lets a plugin module start a system screen and get its result.
iOS plugin API: PamMediaDiskCache.shared.data(source:stableKey:maxAgeMs:completion:)
and PamPrivateFilePath.resolve(root:path:) are public, so the
notifications plugin (a separate Swift module) reads conversation avatars
from the image cache and the private files directory. Before, the moved
plugin did not compile on iOS.
Navigator::interceptSystemBack()
no longer leaves the screen. The released gesture waits for the next
committed frame: a pop completes it, and without one it settles back
(1 s safety timeout). Before, the stack host slid the route away while
PHP kept it, so closing a panel with Back looked like leaving the screen.PixelUtil.toPixelFromSP, through Android 14's non-linear
font scale (TypedValue.applyDimension(SP)); an app text scale applies
to the style first, as RN's StyleSheet patch does. At an OS scale of 1.3
a 20 dp line height is 23.6 dp instead of 26 dp, so multiline text is no
longer taller than in RN. iOS already scales lineHeight linearly like
RN (RCTTextAttributes). A text with no colour is opaque (RN draws
black): the light theme's 87 % primary colour faded colour emoji.pagingEnabled list or scroll)
is full-bleed like React Native and Android. The screen container is no
longer padded 62/34 pt around it, which shrank the pager below the window
while each page stayed one window tall and clipped the bottom chrome of
every page.PAM Native 1.45.1 (on top of 1.45.0) is a fix release. It has no protocol change, and the engine sources are unchanged ( engine=acbeb9d4c734366c , the
PAM Native 1.45.1 (on top of 1.45.0) is a fix release. It has no protocol change, and the engine sources are unchanged (engine=acbeb9d4c734366c, the same as 1.45.0).
useResource() extras. initial: seed data, a cache: ['store' => $adapter] adapter, onSettled()/onPage() events, and manual: true.ViewRef::blur() really moves focus off the input.blurRadius follows the drawn scale, and translucent-edged images blur into transparency instead of showing a square.Gates at the release commit (9e9fdad): PHP SDK run.php, protocol-parity.py, cargo test (CLI, engine, protocol), cargo fmt --check, cargo clippy -D warnings, Kotlin compile with 352 JVM unit tests, iOS XCTest on an iPhone 17e Simulator (Xcode 26.6: 417 tests; the image blur test was updated for the drawn-scale σ, and the HTTP timeout and recycled-cell tests pass on their own), and the release-workflow contracts. Assets are built reproducibly, and the package budgets were verified.
Full list: CHANGELOG.md 1.45.1.
Fixes on top of 1.45.0, no protocol change (core and extension identifiers as in 1.45.0).
Lazy list rows: presses inside a row of a windowed list reach their handlers after the window moves. A row brought back through the compiled fast path no longer resets its owner's active instances (which released every other row on screen), and a row component that leaves the window drops its cached element on unmount, so it renders anew (with live handlers) when it comes back.
iOS VirtualizedList: the bottom padding extends the scrollable content
past the last row (React Native contentContainerStyle, Android
clipToPadding=false), so a list padded to clear floating buttons no
longer ends under them.
Image blurRadius: σ is authored in view points and now follows the
drawn scale (Android multiplied it by the density as well), and an image
with a translucent border blurs into transparency instead of clamping, so
a glyph used as its own shadow no longer becomes a translucent square.
Signals: every watcher, computed value and effect of a signal sees every
change. Signal::set() and ComputedSignal iterated their live observer
WeakMap while each effect detached and re-attached itself on re-run,
which moved it in the map and skipped the next observer: with two or more
watchers each one missed about half of the changes (useResource readers
and key: on a shared signal, computed chains, globals, composables).
Observers are now notified from a snapshot; one disposed earlier in the
same change is skipped. batch() still coalesces the render request, and
an effect still never re-enters itself.
useResource(): initial: shows synchronous data at once (stale, refreshed
behind it); cache: ['store' => $adapter] reads and writes an app's own
cache instead of a second copy; onSettled() and onPage() events;
manual: true never loads by itself, only on load() / reload().
Android navigation: a transition or back gesture never leaves a route
faded, moved or scaled. Every exit path restores the routes it touched:
finished, released early, cancelled, interrupted by another navigation
(also while the gesture settles), the window hidden (app sent to the
background) and the host detached. A navigation that arrived during a back
drag left the route below at the gesture's 0.82–1 alpha, so the whole
screen stayed ~8% darker until a relaunch. A touch only starts the gesture
once it moves past the touch slop along the gesture axis: a tap or a
vertical scroll on a full-screen-gesture route no longer makes the route
below visible and active, nor fires onGestureStart.
Navigator: the back gesture is enabled only when the stack has a route to
go back to. On a stack's root, an edge swipe uncovered the screen mounted
below it by prewarm() (or kept alive) and left it on screen with nothing
popped.
Android ViewRef::blur() moves focus off the input: the window's decor
view gives focus to its descendants first, so parking focus on it handed
it straight back to the first input.
It is backward compatible. The APIs that architecture v2 replaces are @deprecated and keep working, and the core protocol identifiers are unchanged (p…
PAM Native 1.45.0 (on top of 1.44.0) ships architecture v2, the extension protocol table and a long series of Android/iOS parity, memory and performance fixes in one release. It is backward compatible. The APIs that architecture v2 replaces are @deprecated and keep working, and the core protocol identifiers are unchanged (properties 1–543 and events 1–80 are now closed, and new identifiers go to the extension table that starts at 1001).
routes.php (Route::screen/modal/tabs/group/middleware, aliases, keep-alive, error boundaries), App::middleware(), navigate()/back()/redirect(), typed setup() params with Navigator/RouteContext injected, <Link route :params>, and pam-native-routes typed route helpers checked at build time. Also an Axios-style Http::create() client with interceptors, retry, multipart()/upload() progress and cancellable PendingResponse, plus production useResource (persistent scoped cache, reactive keys, last-request-wins, paging). See docs/architecture-v2.md.ProtocolMismatchException instead of sending an ID the renderer would reject. New extension properties: followEndOnResize (1001), ScrollView pageTransform cube (1002), MediaPlayer startBufferMs (1003) and idleSurface (1004), and ScrollView contentOffsetAnimationMs (1005). See docs/protocol-extension-table.md.System\ViewRef (focus/blur/clear/selection/measure), portals, I18n catalogs with plurals, DeviceInfo app version and locale, styled toasts, and TapEffect origin and trigger.checked, MediaPlayer, modals inside tabs and routes, RefreshControl, push and Firebase, image blur, Dynamic Type caps, usageDescriptions, developmentRegion/localizations, and UI driver fling and probe steps.target/pam-native-engine-version (version, protocol=, engine=). pam-native reuses a release engine only when its engine sources match and records engine= in the installed marker.Upgrade note: Component no longer declares an empty setup(), so components can declare setup() with typed parameters. A setup(): void override keeps working, but a parent::setup() call on the old no-op hook must be removed.
Gates at the release commit: PHP SDK run.php, protocol-parity.py, cargo test (CLI, engine, protocol), cargo fmt --check, cargo clippy -D warnings, Kotlin compile with JVM unit tests, iOS XCTest build-for-testing (Xcode 26.6), and the release-workflow contracts. Assets are built reproducibly (renderer, plugin API and PHP SDK byte-for-byte), and the package budgets were verified.
Full list: CHANGELOG.md 1.45.0.
Architecture v2, the extension protocol table and the Android/iOS parity
fixes ship together. Everything is backward compatible: the APIs that
architecture v2 replaces (routes.json, Routing\Route::stack(),
Routing\Navigation, RouteTarget, direct Navigator use, mount() with
own(), effects()/watchers(), initialState()) are @deprecated and keep
working; the core protocol identifiers do not change. Upgrade notes:
Component no longer declares an empty setup(), so a component can declare
setup() with typed route parameters. A setup(): void override keeps
working; only a parent::setup() call on the old no-op hook has to go.
A host that exports a renderer contract makes the PHP SDK refuse an incompatible ABI or protocol at boot; hosts without one keep working with core identifiers.
The Android renderer archive carries its engine marker
(target/pam-native-engine-version: version, protocol= and engine=).
pam-native installs a release engine only when its engine sources match
the local ones and records engine= in the installed marker.
iOS <Switch checked>: the switch follows checked (sent by the template
Switch and Toggle::make), like the Android Switch. It only reached the
accessibility state, so every template switch stayed visually off (a
real-world app's "send in original quality" row said on next to an off
switch).
iOS followEndOnResize (extension property 1001, on by default): a
VirtualizedList opened at its end (initialScrollIndex) or scrolled there
keeps its end visible when its viewport shrinks, even while all of its rows
still fit, as on Android. A real-world app's chat timeline hid its newest
messages behind the composer when the keyboard opened. Inverted lists are
left alone, and followEndOnResize=false turns the behaviour off.
MediaPlayer idleSurface (extension property 1004, Android and iOS):
while true the player, decoder and cache work are released and the poster
covers the view, but the view and its empty video surface stay mounted.
A list cell that plays again, such as a vertical pager neighbour, reuses
that surface instead of building a new video view. In a real-world app's
video pager, creating that view cost ~15 ms of a settle frame on a
Galaxy S10. An idle view never prepares a source, also when it is first
created, and gives its surface buffers back in the background. Only apps
that set it send 1004, so renderers without it keep working. The Android
renderer's property switch also covers the reserved 1001–1003, which
it did not compile without.
ScrollView pageTransform (ScrollPageTransform::Cube, template
pageTransform="cube", extension property 1002): a horizontal paging
ScrollView turns its pages like a cube (Instagram stories): each page
rotates up to 90° around the edge it shares with its neighbour, with
perspective 2.4× the page width, and darkens up to 55% while it turns away.
Android (rotationY/cameraDistance/foreground shade) and iOS
(CATransform3D with m34, shade sublayer) apply it from the scroll offset
on the UI thread, only while the offset changes; pages off-screen are reset.
ScrollView contentOffsetAnimationMs (Scroll::contentOffsetAnimation(),
extension property 1005): a changed contentOffset glides there in that
time (ease-in-out, like RN withTiming) instead of jumping, one offset per
frame (Android ValueAnimator, iOS CADisplayLink), so scroll listeners
and pageTransform run during it and the requested offset stays the
source of truth. The first offset after mount still jumps; a finger down
completes the glide at once (a pager never rests between pages). Property 1004 (MediaIdleSurface) is declared on every
layer to keep the extension table contiguous; its behaviour comes with its
own change.
MediaPlayer startBufferMs (template startBufferMs="350", extension
property 1003): playback starts once that much media is buffered, like
ExoPlayer bufferForPlaybackMs (and resumes after a stall at twice that,
capped by the ExoPlayer default). Android plays such a player through
ExoPlayer; iOS waits on loadedTimeRanges (KVO, no polling) and reports
the wait as buffering.
TapEffect origin (Touch, Center, Anchor), trigger (DoubleTap,
Tap) and armed. TapEffect::pop($ref) plays a squash-and-spring on the
anchor in place on a single tap, on the UI thread before PHP hears the
press, for like/save toggles; armed(false) silences it, and
unlessSelected() silences it while the Pressable is accessibilitySelected
(a toggle that is already on), so the effect string never changes between
renders and a toggle patches one flag. The double-tap heart keeps its
encoding.
iOS MediaPlayer: autoPlay=false on a ready player called the POSIX
pause() (suspending the main thread until a signal) instead of pausing the
player; it now pauses the AVPlayer.
Template event handlers are inferred pure, with no opt-in: a handler method
whose body (and the same-class methods it calls) reads no static or global
state, creates no objects and calls no services, running on a component
whose state holds no objects, skips its component's render when the state
snapshot did not change (React: no state change, no render). Development
builds render anyway and compare; a handler whose skipped render would have
changed the tree gets a PamNativePurity warning and stays impure for the
session. #[PureHandler] still forces purity.
Lazy list rows built by the encoder after their owner rendered stay mounted in later passes when the owner is nested (its ancestors' cached descendant lists were stale: a pass that rendered nothing unmounted the rows and lost their state).
LazyRows::shown() (tests and dev tools): a lazy list's rows as sent,
built rows and placeholders.
Protocol: the core identifier tables are closed (properties 1–543,
events 1–80), and new identifiers go to an extension table that starts
at 1001. Extension IDs use the existing u16 property field, so frames
and golden bytes do not change. Android and iOS hosts export a renderer
contract (PAM_RENDERER_CONTRACT: ABI, protocol range, highest core and
extension IDs). The PHP SDK checks it at boot, refusing an incompatible
ABI or protocol before the first frame. It also checks it while encoding,
and throws ProtocolMismatchException with the property or event name
instead of sending an ID the renderer would reject or ignore. Hosts that
export no contract keep working with apps that use only core IDs.
Properties 1001 (ListFollowEndOnResize), 1002 (ScrollPageTransform)
and 1003 (MediaStartBufferMs) are reserved as constants on every layer;
their behaviour is not part of this change. The parity gate now checks the
extension constants, both tables' sequences and the iOS contract ceilings.
See docs/protocol-extension-table.md.
PHP heap no longer grows over a session. TreeEncoder kept the identity
memo (identityIds, idIdentities, childPaths) of every node ever
encoded, so each route instance, keyed row or sheet stayed for the life of
the process (a real-world app: +1.75 MB per navigation cycle, "Allowed
memory size of 134217728 bytes exhausted (while running Runtime::flush)"
after ~45 min).
Removed nodes are forgotten (ids are XXH3 of the identity, so a node that
comes back gets the same id). A retained element (remembered screen,
memoized row) shown under new paths kept one encoded subtree per path ever
used; only the 2 newest are kept. A mount() that throws releases what it
already owned (subscriptions, listeners, timers), so retried error-boundary
renders no longer stack listeners. Regression test: tests/memory_bounds.php.
Between frames, a PHP heap above 75% of memory_limit runs the cycle
collector at once and logs one warning. Android sets memory_limit from
device RAM as a safety net (128M; 192M from 3.5 GB; 256M from 6 GB;
PAM_NATIVE_MEMORY_LIMIT overrides it). A growing heap is still a leak.
Android runtime: after an idle cycle collection, free Zend MM chunks are returned to the system once more than 8 MB of the PHP heap is unused (iOS bridge parity). A render peak no longer leaves its pages in the process PSS for the rest of the session.
Android: one invalid prop no longer breaks the whole tree. The renderer applies each prop under a guard: a native exception is logged, the prop is skipped, the rest of the batch mounts, and the host shows it as a non-fatal "Native runtime error" in the debug overlay (once per node/prop/message).
Android RefreshControl.progressBackgroundColor takes an ARGB colour. The
container's setProgressBackgroundColor(Int?) resolved to
SwipeRefreshLayout.setProgressBackgroundColor(@ColorRes int) for non-null
values and threw Resources.NotFoundException: Resource ID #0xff1d231e
(any screen with a pull-to-refresh and that colour lost its whole layout
until a force-stop).
Android images: packaged asset:// files up to 16 KiB (icon masks) decode
in the frame and live in the glyph cache like data: icons, so apps can ship
icons as files instead of ~2 KB data: URIs per node in every frame. The
shared image disk cache is capped at 256 MB (RN/Glide budget) even when a
request asks for more.
Android media: a player hidden without being covered (inactive tab kept
attached, GONE subtree, hidden window) releases its MediaCodec, player and
surface after 5 s and resumes at the same position when shown again. The
PamMediaPlayer worker thread ends after 10 s without commands. The media
disk cache keeps at most 256 MB (a request can still allow one file up to
2 GB) and never trims the file it just handed to a player.
Storage::get() and Storage::set() now pass every key through
Storage::safeKey(), like Cache\StoragePersistence already did. Before,
only BoundedStore persistence mapped keys: a direct call with a key
outside [A-Za-z0-9_.-]{1,128} (for example composer:emoji-recents:v1)
reached the native store, which rejected it with "Invalid storage key";
without onError the failure was thrown from the module result and shown
as a runtime error on every read and write. Keys that already match
Storage::KEY_PATTERN are sent unchanged, so stored values keep their
keys. safeKey() is lossy (a:b and a-b share a key): hash owner ids
that must stay distinct.
Modal and
BottomSheet) keeps its text, inputs, buttons, pressables and the end of
its lists out of the status bar, display cutout, navigation bar (gesture
handle or three buttons) and home indicator without a SafeAreaView.
After layout the engine measures how far the content stays from each
inset and pads the surface's content container (the first node of its
single-child wrapper chain) by the missing part only, so the effective
padding is max(inset, padding the app already has): screens and sheets
that clear the bars themselves do not move and nothing is applied twice.
Backgrounds and media keep reaching the edges (wrappers above the
container still span the surface; images and media are not content). The
padding is sticky per container, so a settled surface costs one layout
pass; inset changes (rotation, gesture/three-button switch, multi-window,
cutout) relayout immediately. A SafeAreaView in the wrapper chain keeps
explicit control; one with every edge disabled is the full-bleed opt-out.BottomSheet::make($content, []),
->dynamicSizing() or snapPoints="content" fits the sheet to its content
plus the bottom inset the content does not already clear, capped at the
available height (@gorhom enableDynamicSizing). Android and iOS hosts
take the detent from the engine frame. Requires this renderer (older
Android renderers reject an empty snap list).max(inset, offset)). Stretched or
decorative overlays and nodes inside scrolling content are unchanged.Engine::safe_area_violations(), the CLI
pam-native safe-area-lint <frame>... [--insets l,t,r,b]... [--json] [--explicit-only]
(default: three-button 48 and gesture 24 under a 24 pt status bar; exit 1
on violations) and the PHP helper Pam\Native\Tooling\SafeAreaLint::check()
for app validators and CI.adb logcat -s PamSafeArea; content in a scroll
counts only when it cannot scroll further toward that edge).
adb shell setprop debug.pam.safearea.overlay 1 paints the insets and
outlines offenders; debug.pam.safearea 0 disables it. iOS debug builds
log PamSafeArea: lines (PAM_SAFE_AREA_OVERLAY=1 for the overlay).auto_safe_area_tests (screens, routes, fitted/fixed/
scrolling sheets, FAB, opt-out, sticky padding and runtime inset changes
with three-button, gesture and landscape cutout insets), instrumented
PamSheetSafeAreaInstrumentedTest (three-button and gesture navigation
switched through the system overlays, tall display cutout), PHP SDK
contract (dynamic sizing, SafeAreaLint).Toast::message() takes
borderColor/borderWidth, cornerRadius, accentWidth (0 removes the
left strip), elevation, paddings, minHeight, titleLines (a bold title
on up to 4 lines), fitContent (the card hugs its text inside 16 dp
gutters) and a leading icon: a glyph of an icon font (iconFont,
default Ionicons; new public UI\Icon::glyph()) or a packaged
asset://….png of at most 16 KiB, tinted with iconColor. Defaults keep
the react-native-toast-message card. The iOS offset now counts from the
safe area like Android (a top toast no longer sits under the Dynamic
Island), and a bottom toast rests above the open keyboard on both
platforms. No protocol change.asset:// icons paint in their first frame (Android). A packaged
image of at most 16 KiB (an app's assets/icons, referenced by path
instead of a data: URI) is read once, decoded on the UI thread in the
frame that lays its view out and kept in the inline icon cache, like iOS
PamInlineImages.smallAsset. Larger assets are remembered (bounded set)
and keep the async lane and the photo cache.initialScrollIndex) or a real scroll left it
there; a list at offset 0 inside a sheet or modal that animates its height
keeps offset 0, and inverted lists are never moved. New list prop
followEndOnResize (FlatList/SectionList/VirtualizedList, template
attribute; default true) turns following off. It uses extension PropKey
1001 (ListFollowEndOnResize); iOS lists never follow the end, so the
prop is a no-op there.flexWrap row in a
vertical scroll measures every line: the natural scroll extent uses the
wrapped cross size at the width inside the padding, so the last lines are
no longer cut off and the content can scroll to them.MediaPlayer shows its frame (Android). With autoPlay=false
the MediaPlayer path seeks (SEEK_CLOSEST) to currentTime once prepared
so the surface draws that frame instead of staying black (ExoPlayer and
iOS already did).on:layout, so a Modal (ids derive from keys)
mounted again reports on:layout again and replays its entrance. iOS
already forgot them on remove.wrapping_row_in_a_vertical_scroll_measures_every_line;
PHP SDK (toast style and icon payloads);
instrumented PamListFollowEndOnResizeInstrumentedTest,
PamAssetIconInstrumentedTest, PamInAppToastInstrumentedTest,
PamImeFocusHighlightInstrumentedTest, PamModalRemountInstrumentedTest,
PamMediaPlaybackInstrumentedTest (paused players); XCTest
testToastMessageDecodesCardStyleAndIcon.routes.php with Pam\Native\Route
(screen, modal, tabs, group, middleware, name, prefix,
layout, chained screen options, ->alias(), ->unique(),
->keepAlive(rule), error boundaries), the Middleware interface with
App::middleware() aliases, navigate() / back() / redirect(), typed
setup() params with Navigator/RouteContext injected by type, and the
<Link route :params> template component ({ key: value } object literals
in template expressions). App::run(require 'routes.php') boots them.pam-native-routes routes.php <dir> (run by the CLI before every build)
generates typed RouteName/Routes helpers and a route manifest, and fails
the build on a wrong route name, parameter or literal type in
navigate()/redirect()/<Link>. The CLI derives Android app links and
iOS URL schemes / associated domains from route paths through the new
links manifest key. routes.json, Routing\Route::stack(),
Routing\Navigation, RouteTarget and direct Navigator use are
@deprecated (they keep working).Http::create() returns an immutable HttpClient with
onRequest/onResponse/onError interceptors, timeout, retry for
idempotent requests, multipart() and upload() with progress, immutable
Request (withToken, withHeader, ...), Response (json(), status,
headers), HttpError, and PendingResponse (a Thenable that
useResource() accepts and cancels). Pam\Native\Async\Promise backs it.Keyboard height (Android and iOS): Keyboard::height(), lastHeight(),
metrics() and onChange(fn (KeyboardMetrics $k))/offChange(), like
React Native Keyboard.metrics() and the keyboardWill* events. Hosts
publish one value per settled change (show, hide, a new height such as a
suggestion strip or the emoji keyboard), never per animation frame; the
KeyboardVisibility event payload grows to <visible>;<height>;<durationMs>
(visibility-only payloads are still accepted). onVisibilityChange() is
unchanged.
System\ViewRef (Android and iOS): imperative focus(), blur(),
clear(), setSelection() and isFocused() on inputs and measure() /
measureInWindow() on any view, found by nativeRef (React Native refs).
Calls are sent after the current handler's UI update is committed, so a
caret placed right after changing the value lands in the new text.
Runtime::afterCommit() (internal) queues them.
Portals: <Portal name host> / <PortalHost name> (and UI\Portal::make(),
to(), host()) render content outside the parent tree in the same window,
like @gorhom/portal. A portal lives while its component renders it and is
removed on re-render without it or unmount.
Pam\Native\I18n\I18n: message catalogs per locale (lazy loaders), a
source-locale fallback, {name} interpolation with locale number grouping,
_zero/_one/_other plurals (French n < 2, pluggable rules) and
locale resolution by language subtag. Templates get a t() built-in.
DeviceInfo::$locale carries the system language (BCP 47). See docs/i18n.md.
DeviceInfo exposes the installed appVersion (Android versionName, iOS
CFBundleShortVersionString) and buildNumber (Android versionCode, iOS
CFBundleVersion), so an app can enforce a minimum supported version
(forced-update screen) without a plugin. Both are '' when unknown.
iOS modals: when the app answers a bottom sheet's close request (a tap on
the backdrop) with visible = false while the native dismissal runs, the
repeated hide no longer restarts the dismissal, whose earlier completion
presented the sheet again with the app's emptied content.
iOS Pressable without its own accessibilityLabel announces the labels of
its content, like React Native (RCTRecursiveAccessibilityLabel) and a
focusable Android ViewGroup. A GestureDetector around a labelled button
became an unnamed button that hid the inner label from VoiceOver and UI
tests.
Android navigation bar buttons follow the authored <StatusBar barStyle>
(as React Native apps do when every StatusBar style change also styles the
navigation bar): over the transparent edge-to-edge bar, light-content
gives light buttons and dark-content dark ones, so an always-dark viewer
in the light theme no longer hides the buttons, and light screens in the
dark theme get dark ones. Without a StatusBar style the theme's
pam_light_navigation_bar still applies. An edge-to-edge modal (Android
10+) uses the StatusBar declared inside it; opaque bars keep the theme's
buttons. iOS has no navigation bar (the home indicator adapts itself).
MediaPlayer background suspension (Android and iOS): when the app goes
to the background (Android onStop, iOS didEnterBackground) every player
without keepAliveWhenCovered releases its decoder, player and video
surface, keeping its position and play intent. On resume only a player
with play intent (autoPlay or a native play) is prepared again; a paused
one, such as a warm neighbour in a vertical video pager, is restored on
demand (play or seek). A player given a source while the app is in the
background allocates nothing until it is active again, and its progress
polling stops meanwhile. Before, background only paused the players, so a
real-world app's pager kept two hardware decoders and their buffers alive
while hidden. No protocol change.
MediaPlayer poster (thumbnail): its decoded bitmap is released while
the painted video covers it and decoded again from the cache when the
poster must show (player released, error), also with cache="disk"
(Android kept those posters decoded under the video). No protocol change.
iOS Image: switching a view's source to a local file (pam-file://,
file://, asset://, data:) now cancels the photo-library or network
load started for its previous source. That load used to finish afterwards
and paint the previous picture over the new one, so a recycled thumbnail
cell (a video timeline whose posters are local files) showed gallery
photos. Android already discarded stale loads per view.
Keyboard dock contract (engine test): a padding KeyboardAvoidingView in a
modal rests where its own frame ends (a safe-area padding around it, or
below the window inside scrolled content) and keeps its content exactly
keyboardVerticalOffset above the keyboard. See docs/keyboard.md.
WebView: pages written for react-native-webview work unchanged:
window.ReactNativeWebView.postMessage(text) exists from document start
(Android addJavascriptInterface, iOS document-start script, main frame
only), next to window.PamNative.postMessage. onMessage handlers get the
posting page URL as a second argument (one-argument handlers keep
working). A loaded page runs each new injectedJavaScript once, so the
host can answer the page. scrollEnabled(false) / overScrollMode(Never)
on the existing scroll keys give a fixed page (no scroll, bounce, pinch or
over-scroll). Hardened defaults: no link previews, data detectors,
back/forward swipes, popups, file/content access, mixed content,
geolocation, third-party cookies or zoom controls. Android pauses a
WebView whose route is covered (not only in the background). No protocol
change.
Android device gallery images (MediaStore content://media/...): thumbnails
come from the provider's typed image/* stream at the cell size (Android
10+, cancelled when the cell is recycled or rebound) or its cached MINI_KIND
thumbnail (Android 8-9), decoded as RGB_565 (half the bitmap, also for the
HARDWARE copy). A video is never decoded frame by frame per cell nor read
as image bytes: at any view size (a preview still too) it draws the
platform thumbnail, and without one the load fails instead of reading the
container. No protocol change.
TextScalePolicy::set(maximum, display, displayFontSize): app-wide font
scale caps by typographic role (React Native apps install the same rule in
their theme). Every Text and Input without its own maxFontSizeMultiplier
or allowFontScaling="false" gets the cap of its size, so display text no
longer outgrows body text at accessibility sizes. No protocol change.
iOS single-line Input: the placeholder is no longer indented by the padding twice, and a colored placeholder follows Dynamic Type (it kept the font from before the field joined the window).
Template components: a compiled component's declared props (constructor
parameters, public properties) are no longer also applied as attributes of
its root element. A height prop used as the root's minHeight became a
fixed root height, so a content-sized list cell (a real-world app's profile
summary) stopped growing at large Dynamic Type sizes and overlapped the
next row.
<ScrollView keyboardInset> (iOS and Android): when everything from the
focused field to the end of the content fits above the keyboard, the whole
tail is revealed instead of just the field, so a short form keeps the
button under its field visible, as a resized viewport (a keyboard-aware
sheet) does. In a real-world app's signup the primary button sat under the
iOS suggestion bar. Longer content still reveals only the field.
One list window for every VirtualizedList/VirtualGrid (Android and
iOS). windowSize (React Native FlatList windowSize; template attribute
or ->windowSize(n)) keeps the rows within (n - 1) / 2 screens of the
visible ones built and mounted, a screen being the rows the host reports
on screen; the rows outside are childless ListPlaceholder nodes with the
height (and margins) their row last measured, or estimatedRowHeight
before that, so the content height and the scroll position stay put. Rows
leave and rejoin the window in batches (half a margin of slack), a
scrollRequest with a target offset materializes the rows around it at
once, and rows leaving unmount their components. Static children around
the p-for (a feed header, a footer) are rows of the same window. PHP is
woken by the host's ListWindow event only when a placeholder comes near
the screen (no scroll-phase handlers, no per-frame events). Lists without
windowSize keep the automatic window of long lists (below). The tree
encoders (PHP and native) forget the identities of removed nodes. In a
real-world app's feed after 30 swipes (iOS Simulator, first windowSize
version): PHP memory 51.6 MB to 33.9 MB, encoded nodes 3,688 to 742,
footprint 208 MB to 184 MB.
iOS UI driver (ios-host/UITests): {"fling": "up"|"down"} step, a fast
flick that returns while the list still decelerates (scroll QA).
Bottom sheets: the engine lays out a sheet's content at its current snap point of the window below the top inset, the same rule iOS and Android use for the panel, instead of the whole window. Content that fills the panel (a list over a composer) kept its bottom below the screen.
iOS image blur (blurRadius, CSS blur()): blurred on the CPU with vImage
(three box passes on a copy downscaled so σ stays near 4 px), like
Android's PamBitmapBlur, instead of a Core Image context. A feed of
shadowed icons no longer keeps GPU textures and compiled kernels alive:
in a real-world app's feed MALLOC_LARGE went from 52 MB to 8 MB and the
footprint from 241 MB to 211 MB (peak 342 MB to 234 MB, Simulator).
Engine text metrics: every weight of a variable font shares one copy of the font file instead of reading it once per weight (7.2 MB for seven weights of one family).
iOS Modal / BottomSheet: a modal declared inside a tab scene or a route is mounted on the root host at its absolute engine frame, so later siblings (a real-world app's tab bar) no longer paint over the sheet and hide its bottom; it hides with its logical parent (covered route, inactive tab). Closing a modal ends editing inside it, so the keyboard no longer stays up after the sheet that owned the focused input closed.
iOS images: remote photos far from the screen release their decoded pixels and restore them within one screen of the window (cells beyond the list prefetch, album pages, covered routes, inactive tabs), like Android's shown/detached release; one shared decoded-image cache (identity + pixel size) stops decoding the same photo twice. Encoded bytes keep a quarter of the media memory budget. In a real-world app's photo feed the ImageIO memory went from 161 MB to 26-47 MB and the footprint from 325-395 MB to about 250-260 MB.
iOS PHP runtime: after an idle cycle collection, more than 8 MB of free Zend MM chunks are returned to the system instead of waiting for a memory warning. The first batch perf line reports the OPcache mode and counters.
iOS RefreshControl: UIKit could leave the refresh spinner rotating forever while hidden and not refreshing, which kept Core Animation drawing and UI tests waiting for idle for a minute per step. Outside a pull and a refresh, the control's repeating animations are dropped.
iOS manifest: ios.usageDescriptions (NS*UsageDescription privacy strings
the app needs, e.g. Photos, Contacts, Location, Face ID; app values override
plugin defaults), ios.orientations (portrait-only apps) and
ios.bundleIdentifier (an iOS id that differs from applicationId, used for
the app, extensions, App Group, launch and diagnostics). Without the privacy
strings iOS terminated the app the first time it asked for Photos, Contacts,
Location or Face ID.
iOS media parity with Android (PamMediaView.kt, NativeImageLoader.kt,
the fix/critical-20261014 and fix/ui-polish media fixes):
CGImageSource at the covering view size, on a
background queue, with a small per-animation frame cache (6 MB) that is
purged on memory warnings. One shared 30 Hz display link drives every
animation and stops when none is attached; time only advances while the
image is really on screen (window, no hidden/transparent ancestor, inside
the window bounds). Animations loop forever like AnimatedImageDrawable.MediaPlayer thumbnail() is drawn as a poster over the video until its
first frame is ready (cached as <cacheKey>:thumbnail, like Android), and
the view is transparent instead of black, so feed, reels and stories no
longer flash a black box while the video loads.controls=true; with controls=false touches reach the
app's own gestures (mute, double-tap like, hold to pause).AVPlayerLayer; an
AVPlayerViewController is created only while controls=true.autoPlay=false) and paused seeks draw the exact frame
at currentTime (zero-tolerance seek, Android SEEK_CLOSEST).HIDDEN_RELEASE_MS).on:error reports
"WebM video is not supported on iOS" so the app can show its fallback
(for example a WebM sticker's static image). Android keeps playing them.cacheMaxBytes can lower it, never raise it) and never trims the newest
file, matching NativeMediaFileCache.asset:// images of at most 16 KiB (icon masks) decode once and
stay in the inline glyph cache, like Android's synchronous small assets.PamAnimatedImageTests, PamMediaParityTests.iOS push: Firebase is configured once at install without probing
FirebaseApp.app() first (that probe logs I-COR000003 before
configure()), and registerForRemoteNotifications() is asked at most
once per process: concurrent Notifications::registerPush() calls share
the registration in flight and a cached token no longer re-registers on
every call. A failed or cancelled registration may ask again. Android needs
no change (Firebase initializes from google-services and has no APNs step).
iOS push parity with Android: a GoogleService-Info.plist (.pam/ or the
project root) turns on Firebase Messaging in the generated iOS plugin
package, like google-services.json on Android. registerPush() then
answers with the FCM token and PushProvider::Fcm instead of the raw APNs
token, so FCM-only servers reach iOS. New public hook
PamPushTokenProvider / PamPushNotifications.tokenProvider (plus
didRefresh(token:provider:)); unregisterPush() deletes the provider
token. The host signs aps-environment per configuration through
$(PAM_APS_ENVIRONMENT) (Debug development, Release production),
replacing fixed plugin values. A cached token no longer skips
registerForRemoteNotifications() on later launches. Tests:
PamPushTokenProviderTests (XCTest) and the CLI
ios_push_entitlement_follows_the_build_configuration /
ios_firebase_config_compiles_the_fcm_token_bridge.
iOS manifest: ios.developmentRegion (BCP 47, e.g. pt-BR) and
ios.localizations. The CLI writes them to the Xcode project
(developmentRegion, knownRegions) and to the app Info.plist
(CFBundleDevelopmentRegion, CFBundleLocalizations), so system UI (photo
picker, share sheet, default alert buttons) follows the app's language
instead of English. Omitted, the host template keeps en. Test:
ios_development_region_and_localizations_reach_info_plist_and_project.
Push rendering: route aliases let a screen known by several route ids suppress the pushes of any of them while it is shown (a real-world app's conversation reached by more than one route).
Long lists are materialized by window, with no app change (Android and
iOS): a vertical VirtualizedList/VirtualGrid (or p-for inside
<VirtualizedList>) with more than 96 rows ships its first 48 rows (and
the rows around initialScrollIndex) plus childless placeholder roots,
sized by their authored height or the list estimate. Hosts report the rows
on screen when a placeholder comes within a screen of them and the next
frame turns the rows ahead into full rows in place (same node ids, so
views, decoded images and state are kept). Sticky headers and full-span
rows are always materialized; horizontal and short lists are unchanged.
The window slides: rows more than four margins (256+ rows) away from the
visible ones go back to placeholders (their row components unmount), and
the first 48 rows stay, so memory stays bounded however far a list is
scrolled.
On the framework suite's 10,000-row list (x86_64 API 36 emulator, release
builds, three alternating runs against 1.43.0) the content shows in
~1.0 s instead of ~2.9 s and PSS drops from 336-383 MB to 205 MB, with
frame p99 unchanged at 16 ms; PHP encodes a 424 KB first frame instead of
2 MB, 4x faster with 3.6x less memory. Flinging through placeholders costs
~20% more CPU (each window growth is still an O(rows) patch).
Rows outside the window cost O(1) per run, not per row: a single-column
list sends each run of them as one placeholder node sized rows x the
estimate (ListPlaceholderRows), so PHP, the engine and the host keep
O(window) nodes for any list length. Hosts report the visible rows by
index (also inside a run) and Android keeps the row at the top of the
screen in place while a run splits into rows. A 10,000-row list's first
frame drops from 270 KB / 10,051 nodes to ~3 KB / 50 nodes; encoding it
takes 1.2 ms natively (was 9.1 ms) and 5.1 ms in PHP (was 31.9 ms).
Protocol: properties 541 (ListPlaceholder), 542 (ListWindowed) and 543
(ListPlaceholderRows) and event 80 (ListWindow, consumed by the
runtime; payload @first,last row indexes or legacy node ids) are
appended. Android, iOS, Rust and PHP tables stay in parity.
Rows are rendered only when the window reaches them, with no app change:
a p-for that is the only child of <VirtualizedList>/<VirtualGrid>
(more than 96 items) renders each row when the encoder materializes it,
exactly as the eager loop would (same keys, slots, events and component
instances). Row components mount as children of the component that owns
the template, keep their state by key across re-renders and reorders, and
unmount when they leave the list (or the materialized window). On the
10,000-row list the template screen builds 48 rows instead of 10,000.
VirtualizedList::make() defers closure rows (and generators of them) the
same way, and VirtualizedList::of($items, $row, $key) / VirtualGrid::of()
remain as the data-driven builder (FlatList data + renderItem).
Android renderer: node and frame maps are O(1) (PamLongMap; hashed node
ids made LongSparseArray.put O(n²)); virtual-list row removals/reorders
are applied once per commit and the adapter updates by ranges in one O(N)
walk instead of DiffUtil's O(N+D²); the answer to a press/text change/
submit/toggle jumps the main queue and mounts as soon as it is decoded, so
the next traversal draws it, like a native click handler (it used to wait
for a frame callback, a full frame whenever it landed after a vsync):
touch-to-pixel of a like went from ~47 ms to ~37 ms (native ~34 ms). A filter keystroke over 10,000
rows went from seconds of UI-thread work to milliseconds.
Style::properties() is read natively on Android/iOS (same result, 14x).
Android renderer: re-applying an unchanged layout no longer redraws or
re-lays out the screen (the ancestor invalidation only follows a changed
frame; TextView.setJustificationMode(), which drops the text layout even
for the same mode, is only called on a change; the same safe-area insets
dispatched again skip the subtree relayout). A cold start drew 4 extra
frames after the content (window focus and insets dispatches); now 2.
NavigationContainer::linking() routes the launch URL before the first
frame (Android/iOS export PAM_NATIVE_LAUNCH_URL), without a transition
(no AnimationComplete round trip re-renders the stack after it), and the
Android navigation host lays out and shows the top route in the very first
frame when it is mounted with the host (it used to show the screen under
it first and the deep-linked one a frame later).
Native tree encoder (Android and iOS, transparent): the hosts register a
C++ port of Internal\TreeEncoder and the runtime uses it automatically.
Frames, patches, node ids, callbacks and errors are byte-for-byte those of
the PHP encoder (tests/native_encoder_equivalence.php, run by
scripts/native-encoder-test.sh; PAM_NATIVE_ENCODER=php keeps the PHP
encoder). Re-encoding a rebuilt 43,000-node tree drops from ~257 ms to
~35 ms on the host.
PHP 8.4.27 and 8.5.12 (security releases) are the runtime catalog defaults for Android and iOS.
PAM Native 1.44.0 (on top of 1.43.1) is the iOS parity release. Screens that worked on Android now behave the same on iOS, deep links reach the app, and Intel and Apple Silicon Macs get a Native CLI. No protocol change: no new PropKeys or events (props 1–543 and events 1–80 as in 1.43.1).
Pressable only fired on its own padding: its Row/Column/View content took the touch and UIControl never tracked it, so cards and list rows did nothing. Content containers without handlers are now touch-transparent, as on Android.Input multiline, minLines, textAlignVertical, scrollEnabled, placeholderColor, cursorColor/selectionColor, caretHidden, contextMenuHidden, selectTextOnFocus, debounceMs/syncMode. Text::selectable() and dataDetectorType. Lists: horizontal, inverted, initialScrollIndex, prefetch. Scroll views and lists: scrollEnabled, showsScrollIndicator, contentOffset and keyboardDismissMode. Also pointerEvents, the ActivityIndicator props, Element::animate() without a transition spec, and Pressable pressRetentionOffset.StatusBar backgroundColor paints the band behind the status bar.PamSceneDelegate. PHP starts after the scene connects. Before this, deep links and pam mobile ios:diagnostics/ios:devtools never reached iOS apps.PamNativeUITests target drives the installed app from a JSON step list: tap, swipe, edge-swipe, type, alerts, open URL and screenshot. It needs no GUI session. See docs/ios-ui-driver.md.src/Polyfill/mbstring.php is now mbstring_functions.php. On APFS, exFAT and Windows, the old name collided with the Mbstring class file. The polyfill also keeps UCS-2 units until UTF-8 encoding and rejects surrogate code units.macos-x86_64 and macos-aarch64, and this release ships both binaries.Evidence (iPhone 17 Pro Simulator, iOS 26.5, Xcode 26.6):
PamNative: 309 tests, 0 failures, 3 expected skips.BUILD SUCCEEDED. It needs pam-native-media 0.6.1.Android CI covers API 26 and 36, plus the accessibility evidence.
Guides: docs/ios-parity.md, docs/ios-ui-driver.md.
iOS runtime: OPcache is now enabled in the embedded PHP (JIT stays off: iOS
forbids W^X). Compiled scripts persist in a file cache under
Library/Caches/pam/opcache (never backed up, purgeable), dropped whenever
the app bundle path or build changes; release builds mark sources immutable
(opcache.validate_timestamps=0), debug builds revalidate for hot reload.
Runtimes built before the builder forced the mmap(MAP_ANON) probe have no
shared memory model, so the bridge falls back to opcache.file_cache_only.
iOS runtime: memory_limit follows device RAM like Android (128/192/256M),
capped at a third of os_proc_available_memory();
PAM_NATIVE_MEMORY_LIMIT, PAM_NATIVE_OPCACHE=0,
PAM_NATIVE_OPCACHE_MEMORY override it (PamPhpRuntimeConfiguration).
iOS runtime: memory warnings and going to background now also return the
Zend MM cached pages to the system (gc_collect_cycles + zend_mm_gc, the
gc_mem_caches() of PHP) after the PHP MemoryPressure handlers ran.
iOS runtime: an invalid property value (malformed UTF-8, non-finite
decimal, invalid boolean, malformed list/section/host map, duplicate id) is
skipped and reported as a non-fatal render error instead of dropping the
whole batch (Android guardProperty parity). BatchDecoder.decode stays
strict; the runtime uses BatchDecoder.decodeTolerant.
iOS runtime: [PamNativePerf] firstFrameMs= is logged once per process
(cold start from process creation to the first committed frame).
PHP SDK: the ext-mbstring polyfill functions moved from
src/Polyfill/mbstring.php to src/Polyfill/mbstring_functions.php. The old
name differed from the Mbstring class file only by case, so on
case-insensitive filesystems (macOS APFS, exFAT, Windows) one of the two files
silently replaced the other and mb_* calls or the Mbstring class went
missing on device. Composer autoload.files now points at the new name.
iOS renderer parity (props Android applied and iOS ignored): Input
multiline, minLines, textAlignVertical, scrollEnabled (a
UITextView host that grows with content), placeholderColor,
cursorColor/selectionColor, caretHidden, contextMenuHidden,
selectTextOnFocus, debounceMs/syncMode; Text::selectable() (copy
menu) and dataDetectorType (tel/mailto/http taps); FlatList/SectionList
horizontal, inverted, initialScrollIndex, prefetch; scroll views and
lists scrollEnabled, showsScrollIndicator, contentOffset (applied after
layout) and keyboardDismissMode; pointerEvents (none, box-none,
box-only) on views, pressables, images and text; ActivityIndicator
animating, hidesWhenStopped, size and color; Element::animate()
without a transition spec now animates property changes with the authored
duration/easing; Pressable pressRetentionOffset. Each group ships XCTest
coverage (PamListScrollPropParityTests, PamInputParityTests,
PamTouchParityTests).
iOS: a Pressable only responded on its own padding. Touches on its
Row/Column/View content were claimed by the container view, and
UIControl only tracks a touch whose hit view is the control itself, so the
press never fired (the gallery cards of the showcase did nothing). Content
containers without handlers of their own are now touch-transparent like an
Android View without listeners; a container with its own onPress/gesture
still receives the touch. XCTest testPressableContentContainersAreTouchTransparent.
Navigator: a restored (or reset) stack mounts the route below the top like an idle stack does. After a cold start into a persisted sub-route the iOS back gesture had nothing to reveal and stayed inert until the next navigation; Android's system back hid this.
iOS: the back gesture is a screen-edge recognizer that scroll views wait
for (UIKit's own interactive-pop rule). The previous plain pan never
received the touch on screens with a ScrollView/list, so edge-swipe back
did not work on most screens.
iOS: Text boxes taller than their content centre the lines vertically,
like Android's gravity = CENTER_VERTICAL (fixed-height badges and pills
such as DB, CALL and LAB were pinned to the top). Span presses and
data-detector taps use the same offset.
Showcase: the chat and marketplace screens declare dark status-bar icons on
their light bars, and the LAB/details screens use SafeAreaView.
iOS: a StatusBar committed before the host view joins the window (every
cold start since PHP waits for the scene) is applied once it does. The
showcase gallery's light icons stayed dark on its dark background until the
first navigation. XCTest
testStatusBarCommittedBeforeTheHostJoinsAWindowAppliesOnceItDoes.
iOS: StatusBar backgroundColor paints the band behind the status bar like
Android (translucent keeps it off), so light-on-dark bars stay readable on
light screens.
iOS host: a PamSceneDelegate now receives URL opens, cold-start URLs and
NSUserActivity continuations. Since the UIApplicationSceneManifest was
added in 1.30.0, UIKit delivered those only to a scene delegate, so custom
scheme deep links, universal links and pam mobile ios:diagnostics /
ios:devtools never reached the application delegate on iOS.
iOS host: generated Debug projects now explicitly compile with DEBUG and
-Onone, keeping diagnostics and developer tooling available even when the
embedding Xcode environment does not supply those defaults. Diagnostics
also tolerate a slower Simulator cold launch before reporting no snapshot.
iOS host: a PamNativeUITests target (ios-host/UITests/PamUIDriverTests.swift)
drives the installed application from a JSON step list
(TEST_RUNNER_PAM_UI_SCRIPT: tap by label/identifier/coordinates, swipe,
edge-swipe back, type, system alerts, open URL, wait, screenshot to
TEST_RUNNER_PAM_UI_SHOT_DIR). It is the installed-app Simulator gate the
headless XCTest host cannot provide (safe-area geometry, navigation, sheets)
and needs no GUI session on the build host.
CLI launcher: Intel macOS hosts (Darwin/x86_64) resolve the
macos-x86_64 Native CLI instead of failing with "unsupported host"; the
release workflow now also packages that target.
Runtime catalog: PHP 8.4.27 and 8.5.12 (security releases) replace 8.4.23 and 8.5.8 on Android and iOS.
PAM Native 1.43.1 (on top of 1.43.0) is a performance patch. Idle or hidden work stops waking the app. No API or protocol change.
PAM Native 1.43.1 (on top of 1.43.0) is a performance patch. Idle or hidden work stops waking the app. No API or protocol change.
ActivityIndicator and the Button loading arc started their infinite animator as soon as the renderer created them, even when they were never attached. A spinner in a prewarmed or hidden subtree drove Choreographer frames forever, in the background too. On the Zé Chat inbox (S10), that meant about 60 main-thread wakeups/s and 4-5% CPU while idle. The loop now runs only while its host is attached, shown and in a visible window. It pauses when the host leaves and resumes on its next draw. iOS spinners already animated only inside a window.ScrollView offset requests wait for layout (Android). A requested content offset (contentOffsetX/Y, initial offsets, scroll requests) on a container that is not laid out yet (GONE, never measured, or still without content) is now applied on the container's next layout. Before, it re-posted itself to the UI thread on every looper iteration for as long as the container stayed unlaid. With a feed video playing, this kept the main thread at about 64% CPU. iOS applies offsets from layout and has no such retry.DeviceStatus::watch() delivers changes only. The first status is delivered, then only changes. Android replaces the per-interval main-thread poll (three binder calls and a PHP callback every interval, in the background too) with the default network callback and the battery/power-save broadcasts. Changes closer together than the interval are coalesced. iOS keeps its timer but drops unchanged samples.Navigator::prewarm($route, $params, releaseAfterMs: null). With null, the warm screen stays until another navigation, cancelPrewarm() or trimMemory(), instead of being released after 4 s unused. A screen that keeps its first row warm while idle no longer renews it with a timer. Each renewal woke PHP and ran two render passes, about 40 wakeups/min on the Zé Chat inbox. The default stays 4 s. This change is PHP only.speed-profile the playback loop no longer runs interpreted. On the S10, a feed video went from 66% to 56% process CPU (ExoPlayer playback thread 13% → 9%, codec callbacks 9.5% → 6%).Guides: docs/navigation.md (prewarm), docs/production-capabilities.md (DeviceStatus), docs/ios-parity.md (Mac checklist). Tests: instrumented PamOffscreenSpinnerInstrumentedTest and PamScrollOffsetWaitInstrumentedTest, JVM DeviceStatusChangesTest, XCTest DeviceStatusChangesTests (not compiled on Linux), and the PHP SDK contract.
speed-profile the playback loop no longer
runs interpreted. A feed video on the S10 went from 66% to 56% process CPU
(ExoPlayer playback thread 13% → 9%, codec callbacks 9.5% → 6%).ScrollView: a requested content offset (contentOffsetX/Y,
initial offsets, scroll requests) on a container that is not laid out yet
(GONE, never measured, or still without content) waits for its next layout.
It used to re-post itself to the UI thread on every looper iteration for as
long as the container stayed unlaid: on the Zé Chat feed, with a video
playing, the main thread sat at ~64% CPU. iOS applies offsets from layout
and has no such retry.ActivityIndicator and the
Button loading arc started their infinite ValueAnimator as soon as the
renderer created them, before (or without ever) being attached: a spinner
in a prewarmed or hidden subtree drove Choreographer frames forever, also
with the app in the background (Zé Chat inbox on the S10: ~60 main-thread
wakeups/s, 4-5% CPU idle and in background). The loop now runs only while
its host is attached, shown and in a visible window, pauses when the host
leaves and resumes on its next draw. iOS spinners already animate only in a
window.DeviceStatus::watch() delivers the first status and then only changes.
Android drops the per-interval main-thread poll (three binder calls and a
PHP callback every interval, in the background too) for the default
network callback and the battery/power-save broadcasts; changes closer
than the interval are coalesced. iOS keeps its timer and drops unchanged
samples. Mac checklist in docs/ios-parity.md.Navigator::prewarm($route, $params, releaseAfterMs: null) keeps the warm
screen until another navigation, cancelPrewarm() or trimMemory()
instead of releasing it after 4 s unused. A screen that keeps its first
row warm while idle no longer renews it with a timer (every renewal woke
PHP and ran two render passes: ~40 wakeups/min on the Zé Chat inbox). The
default stays 4 s. PHP only.PAM Native 1.43.0 (on top of 1.42.1) makes native photo zoom behave like a photo viewer and fixes taps on zoomed content on Android.
PAM Native 1.43.0 (on top of 1.42.1) makes native photo zoom behave like a photo viewer and fixes taps on zoomed content on Android.
gestureNativeBounds="true" and gestureNativeContentAspect on a native-transform GestureDetector (nativeTransform(bounds:, contentAspect:)) keep the zoomed photo covering the viewport. While panning or pinching, the translation stops at the edges of the scaled content, which is either the child itself or the rectangle a resizeMode="contain" image draws inside it. Content smaller than the viewport on an axis stays centred. Reversing a drag moves the photo immediately. On release, the last bounded gesture on the surface springs it to rest. At or below 1.02x it returns to the centred identity; above that it stays inside the bounds, up to gestureNativeMaxScale. Set gestureNativeMinScale below 1 so a pinch can shrink the photo before it springs back. End events report the resting nativeScale/nativeTranslationX/Y, so a PHP commit always matches the screen. Before, a PHP clamp equal to the previous commit produced no property change, and the native view kept the unclamped translation, showing black past the photo.Pressable decides whether a touch belongs to an independent child control. It mapped the touch point with the child's translation only. Under a scaled child, it stole the touches outside the untransformed box, so double-tapping a zoomed photo to zoom out failed on most of the screen. The point now goes through the child's full matrix (scale, rotation, pivot), the same way ViewGroup hit testing works. iOS already used UIKit's transform-aware hit testing.GestureNativeBounds) and 540 (GestureNativeContentAspect) are added to PHP, Rust, Android and iOS.Guide: docs/gestures.md ("Bounded photo zoom"). Tests: JVM PamPressableGestureTest (contain geometry and bounds), instrumented PamPressableNativeTransformInstrumentedTest (bounded pan and resting payload, zoomed tap target), XCTest testBoundedPhotoTransformKeepsTheContainedContentCoveringTheViewport (not compiled on Linux), and the PHP SDK contract.
gestureNativeBounds and
gestureNativeContentAspect on GestureDetector (and
nativeTransform(bounds:, contentAspect:)), property keys 539/540. Pan and
pinch keep the scaled content (the child, or the contained image rectangle)
covering the viewport, a reversed drag responds at once, and on release the
surface springs to rest: at or below 1.02x back to the centred identity,
otherwise inside the bounds. End events report the resting values. Android
and iOS.Pressable on Android: the
independent-touch-target probe mapped the point with the translation only,
so outside the untransformed box the detector stole the touch (a zoomed
photo's double tap to zoom out failed on most of the screen). It now maps
through the child's full matrix like ViewGroup hit testing.PAM Native 1.42.1 is an Android and iOS host fix: a PHP error can no longer end the app process. The PHP SDK, protocol and engine are the same as in 1
PAM Native 1.42.1 is an Android and iOS host fix: a PHP error can no longer end the app process. The PHP SDK, protocol and engine are the same as in 1.42.0. Only the version number changes for them.
The crash. Some PHP errors cannot be turned into an exception, such as an exhausted memory_limit, E_USER_ERROR or a compile error. When one of them, an exception that escaped the runtime, or a call to exit()/die() happened outside the app entry (in an event handler, render, cycle collection or shutdown), it reached zend_bailout() with no bailout address. PHP then called exit(-1). The app died with code 255, and the C++ static destructors ran on the PHP thread while the render thread was still drawing. Logcat showed ~EglManager() leaked an EGL context, then FORTIFY pthread_mutex_lock called on a destroyed mutex. Zé Chat hit this during pull to refresh. Before this fix, the bridge's own "Unhandled PHP exception" reports could never run.
The fix. The Android and iOS bridges now run every PHP entry point of the worker under a bailout guard. When PHP abandons a request, the bridge:
PAMERR1 error (PHP Fatal error, PHP Parse error or PHP exit, phase terminated) with PHP's message, file and line;Debug builds open the error inspector, where Reload starts a fresh request. Release builds retry with backoff, then show the friendly fallback. Closing a failed runtime shuts PHP down cleanly, so the next runtime in the process can boot again. The bridges also detect a fatal error or exit() in the app entry: php_execute_script() returns bool, so the old FAILURE comparison never matched. They now check that the optional Runtime::checkpointHotReload() and shutdown() methods exist before calling them.
Validation on candidate 5488f7fb (based on v1.42.0):
exit() or an exception escaping the runtime in an event handler gives Zygote: Process ... exited cleanly (255), the same exit code as in the field.PamPhpFatalRecoveryInstrumentedTest passes 6 of 6. It covers exit(), memory exhaustion and an escaping exception in an event, memory exhaustion and exit() in the entry, and closing a failed runtime. In each case there is exactly one fatal report, the process survives and the next reload runs.cargo fmt --check is clean. The PHP SDK suite and protocol parity pass. The new scripts/test_php_bailout_guard.py (now in CI) checks that every PHP call in the worker is guarded and that Android and iOS share the same guard code.Known limits:
testBridgeBailoutReportsAreFatal) is included, but Xcode/iOS execution was not available on Linux.~EglManager/FORTIFY lines are a race with the render thread. I did not reproduce them on the emulator. The exit code and the PHP-thread exit path match the field crash.PamNativeErrors logcat tag (release) instead of killing the app.Android and iOS host fix; PHP SDK, protocol and engine are unchanged from 1.42.0 (only the version moves).
E_USER_ERROR, compile errors), an
exception escaping the runtime, or exit()/die() in an event handler,
render, cycle collection or shutdown reached zend_bailout() without a
bailout address: PHP called exit(-1), the app died with code 255 and the
C++ static destructors ran under the live render thread
(~EglManager() leaked an EGL context, then FORTIFY
pthread_mutex_lock called on a destroyed mutex), as seen on Zé Chat
during pull to refresh.PHP Fatal error,
PHP Parse error or PHP exit, phase terminated, with PHP's message,
file and line), drop the events queued for it and wait for the next
reload: debug builds open the error inspector, release builds retry with a
fresh request. Closing a failed runtime shuts PHP down cleanly.exit() in the app entry is detected too
(php_execute_script() returns bool; the old FAILURE comparison never
matched). Optional Runtime::checkpointHotReload()/shutdown() are probed
before being called.PamPhpFatalRecoveryInstrumentedTest (exit, memory exhaustion and an
escaping exception in an event; memory exhaustion and exit in the entry;
closing a failed runtime), scripts/test_php_bailout_guard.py (every PHP
call of the worker is guarded, Android and iOS share the guard) and an iOS
report-parsing XCTest.PAM Native 1.42.0 adds media-library thumbnails, file existence checks, raw drag drivers, accessibility selection, keyboard tap persistence on scroll
PAM Native 1.42.0 adds media-library thumbnails, file existence checks, raw drag drivers, accessibility selection, keyboard tap persistence on scroll views and lists, per-route error boundaries, a native "new contact" form, multi-button alerts with permission rationale, and failure callbacks in place of exceptions across several system modules. Protocol: properties 537 (accessibilitySelected) and 538 (keyboardShouldPersistTaps), append-only. The other additions are new module methods and need no protocol change. Existing calls behave as before.
Media library
MediaAsset now has a thumbnailUri, the source to use for a grid cell.
Image decodes it at the view size from the platform thumbnail cache, and videos show a frame.phasset:// source, drawn at the view size. Videos show their poster frame.MediaLibrary::thumbnail($assetId, $maxPx, $done, $failure) writes a JPEG and returns its file:// URI.
$maxPx (clamped to 32-1024), and video frames are supported.loadThumbnail, older versions use a sampled decode or getScaledFrameAtTime, and iOS uses PhotoKit.assets(..., failure:) and albums(..., $failure) pass native failures, such as a missing permission, to the closure instead of throwing.refreshLimitedSelection(fn (bool $limited) => ...) reopens the system selection when photo access is limited: iOS 14+ presents the limited library picker, and Android 14+ requests the visual media permissions again.Files
Files::exists($path, fn (bool $exists) => ...).Files::find(), which returns ?FileReference.Files::stat() no longer throws when the file is missing. It calls the optional missing closure instead; other failures go to failure.Gestures
Drag::driveRaw() drives a property from the raw finger translation, before bounds and rubber band are applied, and extrapolates past its points.driveUnbounded() makes every drive() behave the same way.Accessibility
accessibilitySelected / Element::accessibilitySelected() reports selection to TalkBack (AccessibilityNodeInfo.isSelected) and VoiceOver (.selected trait) without changing the visual selected state.Keyboard
keyboardShouldPersistTaps works on ScrollView, FlatList, SectionList and VirtualizedList, as in React Native, through the new KeyboardPersistTaps enum:
never: a tap dismisses the keyboard and is consumed.handled: the keyboard is dismissed only when no child handles the tap.always: taps never dismiss the keyboard.Navigation
PendingRoute::errorBoundary() and Router::errorBoundary(), plus a global default with Route::errorBoundary().$retry() renders the route again, and the error is reported once as non-fatal.System
Contacts::openNewContactForm(fn (bool $created), $failure) opens the system editor: Android ACTION_INSERT, iOS CNContactViewController. It needs no contacts permission.Share::text() gains $failure, and $opened now fires only after the sheet has actually been presented.Alert::choose() shows 1-3 AlertButtons with the styles Default, Cancel and Destructive, and returns the index of the pressed button.Permissions::shouldShowRationale().requestKind(..., rationale: new PermissionRationale(...)) first explains a repeated request in a native alert.Permissions::status()/requestKind() and Caches::usage()/clear() accept a $failure closure.Validation of candidate
tests/mbstring_polyfill.php still differs from the local PHP 8.4.24 ext-mbstring; this host difference was already present in 1.40 and 1.41.lintDebug pass.accessibilitySelected, contacts, native capabilities).native and native-ui community first-run gates passed on the API 36 emulator (isolated dev port 39142).Known limits
docs/ios-parity.md (1.42.0 sections).Alert::choose, the rationale dialog, keyboardShouldPersistTaps taps and the Android 14 selection picker. They are covered by JVM and PHP tests only.pinchZoom, maxZoom, zoomResetRevision, ready with min/max zoom, doubleTap/doubleTapFlip) belong to the pushinbr/pam-native-media plugin and ship as its own 0.6.0, not in this release.Protocol: property 537 (accessibilitySelected) and 538
(keyboardShouldPersistTaps), append-only. New module methods need no
protocol change.
MediaAsset carries thumbnailUri (Android
the typed images/video MediaStore URI that Image decodes at the view size
from the platform thumbnail cache, videos as a frame; iOS the phasset://
source drawn at the view size). MediaLibrary::thumbnail($assetId, $maxPx, $done, $failure) writes a JPEG of at most $maxPx (32-1024) on its longer
edge, video frames included, decoded at that size (Android 10+
loadThumbnail, sampled decode or getScaledFrameAtTime before; PhotoKit
on iOS) into a bounded disk cache (24 MiB / 600 files, LRU trimmed to 75%,
keyed by the asset's modification date) and reports its file:// URI.MediaLibrary::assets(..., failure:) and albums(..., $failure): native
failures (missing permission, closed module) reach the closure instead of
throwing.MediaLibrary::refreshLimitedSelection(fn (bool $limited) => ...): with
limited photo access, shows the system selection again (iOS 14+
presentLimitedLibraryPicker, Android 14+ re-request of the visual media
permissions); full or no access completes at once without UI.Files::exists($path, fn (bool $exists) => ...) and Files::find()
(?FileReference); Files::stat() no longer throws for a missing file: it
calls the new optional missing closure (or nothing), other failures go to
the optional failure closure.Drag::driveRaw() drives a property from the raw finger translation (before
bounds()/rubberBand()) and extrapolates past its points;
driveUnbounded() makes every drive() of the drag behave that way.accessibilitySelected (Element::accessibilitySelected()): announces
selection to TalkBack (AccessibilityNodeInfo.isSelected) and VoiceOver
(.selected trait) without the visual selected state; it wins over
selected for assistive technology only.Contacts::openNewContactForm(fn (bool $created), $failure): system
"new contact" editor (Android ACTION_INSERT, iOS
CNContactViewController(forNewContact:)), no contacts permission needed;
failures go to $failure.Share::text() gains ?Closure $failure; $opened now fires only once the
sheet was presented (iOS answered before presenting; failures no longer
call $opened).Alert::choose() with 1-3 AlertButtons (AlertButtonStyle
Default/Cancel/Destructive) answering the pressed index (Alert::DISMISSED
= -1); optional keys on the existing Alert operation.Permissions::shouldShowRationale() (Android
shouldShowRequestPermissionRationale, iOS always false) and
PermissionRationale: requestKind(..., rationale:) explains a re-request
in a native alert first; cancelling answers the current status.Permissions::status()/requestKind() and Caches::usage()/clear() accept
?Closure $failure; with it native failures are delivered instead of
thrown (still thrown without it).PamActivity.launchForResult drops its callback when the launch
throws and pending activity-result callbacks are cleared on destroy; open
choice alerts and contact forms are failed/dismissed when their module
closes.keyboardShouldPersistTaps on ScrollView, FlatList, SectionList and
VirtualizedList, as in React Native: never (a tap dismisses the keyboard
and is consumed), handled (dismisses only when no child handles the tap)
and always, plus RN's booleans; enum KeyboardPersistTaps. Without the
attribute the current behaviour stays (a tap never closes the keyboard);
nothing is installed when absent or always.PendingRoute::errorBoundary(),
Router::errorBoundary() and the global Route::errorBoundary() render a
fallback in place of a stack route that throws while created, mounted or
rendered; other routes and tabs keep working, $retry() renders the route
again and the error is reported once as non-fatal. Direct Route::tab() /
drawerScreen() items have no boundary.PAM Native 1.41.0 (on top of 1.40.0) makes covered routes lean by default and fixes scroll requests that landed short.
PAM Native 1.41.0 (on top of 1.40.0) makes covered routes lean by default and fixes scroll requests that landed short.
MediaPlayer in it frees its player, decoder (ExoPlayer/MediaPlayer + MediaCodec, AVPlayer), video surface and progress loop. It comes back at the same position and play intent when the route is visible again. Contained modals and form sheets keep the route below them playing. A player can opt out with keepAliveWhenCovered. Apps no longer have to release players themselves before pushing; Zé Chat's ReleasesMediaWhenCovered workaround is no longer needed.on:routeCovered and on:routeFocused (onRouteCovered()/onRouteFocused() on any element) fire natively once per change, including in nested navigators and tabs.ScrollView, FlatList, SectionList and VirtualizedList jump. A scroll to the top used to stop about 40 px short on Android. Offset 0 on Android virtual lists is now the real top (it used to resolve to 1 px). iOS deceleration is stopped the same way. The new scrollAnimated (scrollRequest(..., animated: true)) glides to the target and then snaps onto it exactly. iOS lists now jump by default instead of always animating.#[PureHandler]. Template method handlers and element closures with this attribute do not mark their component dirty. The runtime renders after them only when that component's state, a tracked store or signal, or an explicit request changed. Timer-like events no longer re-render the screen.<Text mediaClock="ref" mediaClockFormat="remaining|elapsed|elapsed-duration|duration|countdown"> and mediaProgress="ref" (Text::mediaClock(), Element::mediaProgress(), MediaClockFormat) follow a player's position natively. PHP gets no tick, and nothing updates while the player is paused or its route is covered.Validation:
route_coverage.php, plus the performance, visual DOM, navigation and fuzz suites.native and native-ui community first-run gates passed on a clean emulator (screenshots in gate-evidence/). The server journeys need host PHP 8.5, which this machine does not have, so they were not run here.Not covered:
PamCoveredRouteTests were not compiled, because Xcode is not available on Linux. The Mac checklist is in docs/ios-parity.md.PamReloadModuleResultInstrumentedTest.shutdownCompletionsCannotConsumeNewLinkingRequestIds crashes the test process on the v1.40.0 baseline too (the app process exits after PHP entry execution returned). It was excluded from the run. This looks like the PHP exit crash being investigated on fix/php-exit-crash, not this change.mbstring_polyfill check differs on host PHP 8.4.24. This happened before this change and does not affect the shipped SDK.keepAliveWhenCovered. Apps no longer need to release
players before pushing (Zé Chat's ReleasesMediaWhenCovered).on:routeCovered/on:routeFocused (onRouteCovered()/onRouteFocused()
on any element): native, edge-triggered route coverage events, also inside
nested navigators and tabs; a view mounted covered reports it once.ScrollView, FlatList, SectionList and VirtualizedList jump
(a scroll to the top used to stop ~40 px short), offset 0 on Android
virtual lists is the very top (it resolved to 1 px), and iOS deceleration
is halted the same way. New scrollAnimated / scrollRequest(..., animated:)
glides there and snaps exactly; iOS virtual lists no longer animate every
request by default.#[PureHandler] event handlers (template methods and element closures) do
not mark their component dirty: the runtime renders after them only when
its state, a tracked store/signal or an explicit request changed, so
timer-like events no longer re-render the screen.<Text mediaClock="ref" mediaClockFormat="remaining"> and mediaProgress="ref" (Text::mediaClock(),
Element::mediaProgress(), MediaClockFormat) follow a player's position
natively with no PHP tick, nothing while paused or covered.PamCoveredRouteTests (Mac validation
checklist in docs/ios-parity.md).PAM Native 1.40.0 moves the app plumbing that every production app ends up hand-writing into the SDK: event buses, timers that stop with their screen,
PAM Native 1.40.0 moves the app plumbing that every production app ends up hand-writing into the SDK: event buses, timers that stop with their screen, rate limiters, bounded caches, optimistic overlays, display formatting, progressive list windows and a durable offline queue. It is a pure PHP release. The Android and iOS hosts, the protocol and the native engines are unchanged from 1.39.4, whose delta hot reload this release includes; only the version moves. Guide: docs/app-infrastructure.md. Example: examples/showcase/src/InfrastructureDemo.php.
Ownership. Disposable, Component::own() and the owner: arguments release subscriptions, timers and rate limiters when a component unmounts. Subscription::from() adapts id-based APIs such as App::onStateChange().
Events. Events\EventBus supports named and typed events, once(), shared buses (emptied on hot reload), a listener bound and error isolation. Events\Observable is a Signal-backed value with change listeners.
Component timers. Component::timers() provides timeout, every, ensure, debounce and throttle.
TimerBackgroundPolicy (Suspend, Cancel or Continue).restart(), onCancel and onFinish hooks and failure handlers.Rate limiting.
Scheduling\Debouncer has maxWait, flush, setDelay and markSent.Scheduling\Throttler has leading/trailing calls, rearm: false batching windows, setInterval and markSent.Scheduling\SingleFlight joins concurrent callers, supports an again refresh and bounds its keys.Caches.
Cache\BoundedStore is an LRU cache with max items, TTL, a byte budget and account scope. It provides get/peek/put/replace/forget/remember/trim/persist/hydrate.Cache\IdLedger is a bounded id set with TTL.CachePersistence: StoragePersistence, CallbackPersistence (for Nitro or other stores) or MemoryPersistence. Snapshots are trimmed to the backend's maxValueBytes().Storage\StorageBudget together with Storage::MAX_VALUE_BYTES, KEY_PATTERN and safeKey() handles the native limits: 256 KiB per value and keys matching [A-Za-z0-9_.-]{1,128}.Optimistic UI. Store\OptimisticOverlay provides begin/settle/rollback/set/apply/applyAll.
dropSettled() can drop entries by revision or by age.Formatting. Support\Format provides count, countLabel, compact, relative (Short/Long/Narrow/Tiny), date/dateTime with DateStyle, bytes, duration and time. It covers pt-BR and English without ext-intl. Support\Text provides fold, foldWithMap, contains and length; folding is NFD-equivalent for Latin, Greek and Cyrillic.
Lists. Support\ProgressiveListWindow builds viewport-first windows using row or cost/height budgets. admitLeading handles rows inserted at the top. Deferred rows join on the next frame through a component timer.
Offline queue. Sync\OfflineMutationQueue adds:
BackoffPolicy, with base, cap, factor, jitter and maxAttempts.dedupeKey coalescing of unsent intents.stored/failed write callbacks, batch(), clear(), createdAtMs and all($operation).hydrate()/persist(). Interrupted sends are restored as Retry.drainOn() triggers: Enqueue, Connectivity, Foreground and RetryDue. They run only while mutations are pending and the app is in the foreground.Existing calls keep their behaviour.
Validation on candidate 7c5f3502 (rebased on v1.39.4):
native and native-ui community first-run gates on the API 36 emulator (isolated dev port 39102): pam init, pam dev, launch, clean logcat and a PNG capture.Known limits:
native timed out because the launcher held the foreground (no crash in logcat). A clean rerun passed both surfaces; the evidence is from that run.tests/mbstring_polyfill.php differs from the local PHP 8.4.24 ext-mbstring on mb_strrpos with negative offsets. It behaves identically at 1.39.3 and 1.39.4, so this is a host difference, not a 1.40 change.Pure PHP SDK release: Android and iOS hosts, the protocol and native artifacts are unchanged from 1.39.4 (only the version moves).
Events\EventBus (named and typed events, once(), shared buses,
bounded listeners, error isolation) and Events\Observable (Signal-backed
value with change listeners). on() returns a Subscription.Disposable, Component::own() and owner: arguments: subscriptions,
timers and rate limiters owned by a component are released on unmount.Component::timers() (ComponentTimers): timeouts and intervals that
cancel on unmount and follow TimerBackgroundPolicy (Suspend by default,
re-armed on resume with the wall-clock time left), ensure(), restart(),
onCancel/onFinish hooks, failure handlers, delays longer than a day,
plus owned debounce() and throttle().Scheduling\Debouncer (maxWait, flush, setDelay, markSent),
Scheduling\Throttler (leading/trailing, rearm: false batching windows,
setInterval, markSent) — both with injectable scheduler/clock and failure
handlers — and Scheduling\SingleFlight (joined callers, again refresh,
bounded keys).Support\ProgressiveListWindow: viewport-first list windows (row or
cost/height budgets, admitLeading for top inserts) whose deferred rows
join on the next frame through a component timer.Cache\BoundedStore (LRU with max items, TTL, byte budget, account
scope, get/peek/put/replace/forget/remember/trim/persist/hydrate) and
Cache\IdLedger (bounded id set with TTL), persisted through
Cache\CachePersistence (StoragePersistence, CallbackPersistence for
Nitro or other stores, MemoryPersistence) with snapshots trimmed to the
backend's maxValueBytes().Storage\StorageBudget (trimList/encodeList/encodeMap/encodeObject)
and Storage::MAX_VALUE_BYTES/KEY_PATTERN/safeKey() for the native
256 KiB value and [A-Za-z0-9_.-]{1,128} key limits.Store\OptimisticOverlay: begin/settle/rollback/set/apply/applyAll,
revision- and age-based dropSettled(), change-only listeners and LRU that
never evicts in-flight entries.Support\Format (count, countLabel, compact, relative with
Short/Long/Narrow/Tiny styles, date/dateTime with DateStyle, bytes, duration,
time; pt-BR and English, no ext-intl) and
Support\Text (fold, foldWithMap, contains, length).Sync\OfflineMutationQueue: BackoffPolicy (base, cap, factor,
jitter, maxAttempts), dedupeKey coalescing of unsent intents, stored/
failed write callbacks, batch(), clear(), createdAtMs, persistence
with hydrate()/persist() (interrupted sends restored as Retry) and
drainOn() triggers (Enqueue, Connectivity, Foreground, RetryDue) that run
only while mutations are pending in the foreground. Existing calls keep
their behaviour.docs/app-infrastructure.md; example:
examples/showcase/src/InfrastructureDemo.php.pam dev hot reload has no bundle size limit anymore. The CLI serves a content-addressed manifest; the first sync streams only the files the device lac
pam dev hot reload has no bundle size limit anymore. The CLI serves avendor/ is resent only when Composer changed it..pam.php file in Zé Chat (2,100 files) updates the S10 screen in about#[State] of mounted components survives a hot reload bymount(); props, objects and plainadb reverse afterpam native dev:serve serves an installed apppam_native_runtime_reload_prepared) andscripts/test_hot_reload_large_app.py (end-to-end,PAM Native 1.39.3 adds React Native pull to refresh directly on scroll views and lists, a native page-change event for pagers and carousels, RN-parity
PAM Native 1.39.3 adds React Native pull to refresh directly on scroll views and lists, a native page-change event for pagers and carousels, RN-parity memory trimming, and zero-height empty virtual-list cells. It also includes the IME, focus, stacking and sheet-keyboard fixes prepared after 1.39.2.
Pull to refresh. Set :refreshing, on:refresh, tintColor, refreshColors, progressBackgroundColor, progressViewOffset, refreshIndicatorSize and refreshEnabled directly on ScrollView, VirtualizedList, FlatList or SectionList. You can also use the fluent refreshing() and onRefresh() methods. PAM wraps the scrollable in a native RefreshControl host automatically. Android now uses SwipeRefreshLayout (new dependency androidx.swiperefreshlayout:1.1.0) and iOS uses UIRefreshControl. A pull starts only at the top and still works on empty or short content. Horizontal gestures never start a pull, and the controlled refreshing value always wins. See docs/pull-to-refresh.md.
Page change. on:pageChange / onPageChange() (PageChangeEvent: page, previousPage) fires once when the current page changes during the drag. It is never sent per frame.
Memory. Android onTrimMemory empties caches only on RUNNING_CRITICAL/COMPLETE. UI_HIDDEN/BACKGROUND halve them. iOS halves the media memory cache on entering background and still empties it on memory warnings.
Layout. A mounted VirtualizedList cell with empty or hidden content measures 0. Only unmounted cells use the row estimate.
Protocol additions are append-only: EventKind 77 PageChange, PropKey 528 OnPageChange and 529 RefreshEnabled.
Validation on candidate 79f51e19:
native and native-ui community first-run gates passed on API 36: pam init, pam dev, launch, clean logcat and a PNG capture.Known limits:
PamKeyboardDismissInstrumentedTest.explicitBackKeepsImeClosedWithRetainedHeightAvoidingInput fails on an API 31 emulator. It fails identically at the pre-change base 31314653, so it is pre-existing and API 31 specific. It passes on API 36 both at the base and at this candidate.RefreshControl behavior straight on ScrollView,
VirtualizedList, FlatList and SectionList (:refreshing,
on:refresh, tintColor, refreshColors, progressBackgroundColor,
progressViewOffset, refreshIndicatorSize, refreshEnabled), lowered to
a native host automatically. Android now uses SwipeRefreshLayout and iOS
UIRefreshControl: pulls start only at the top, work on empty/short content,
ignore horizontal gestures, and the controlled refreshing always wins.on:pageChange/onPageChange() (PageChangeEvent) to scroll views and
lists: fires once when the current page changes mid-drag, never per frame.onTrimMemory now empties caches only on RUNNING_CRITICAL/COMPLETE
(RN parity); UI_HIDDEN/BACKGROUND halve them. iOS halves the media memory
cache on entering background and still empties it on memory warnings.PAM Native 1.39.2 fixes retained hidden editors holding IME focus and generating invisible redraw work. Android cancels hidden autofocus and restores
PAM Native 1.39.2 fixes retained hidden editors holding IME focus and generating invisible redraw work. Android cancels hidden autofocus and restores autofocus when visible modals are remounted. iOS navigation resigns editors within hidden route subtrees without affecting destination focus.
Validation: 229 Rust tests, full PHP SDK, protocol parity plus 5 regression tests, 277 Android JVM tests, 26 Android navigation/keyboard instrumented cases on API 36, and exact-candidate native/native-ui first-run gates with PHP/Kotlin/engine provenance. Linux CLI, Android renderer, PHP SDK archives and plugin AAR pass deterministic rebuilds and package budgets.
Three iOS XCTest cases are included, but Xcode/iOS execution was unavailable on Linux. API 26 was not rerun for this focused patch. Application-specific idle-frame remeasurement remains a separate integration check after installing this official release.
PAM Native 1.39.1 fixes Android Activity recreation while the PHP runtime remains alive. Push, notification-action, deep-link and incoming-share subsc
PAM Native 1.39.1 fixes Android Activity recreation while the PHP runtime remains alive. Push, notification-action, deep-link and incoming-share subscriptions survive surface replacement. Context-free timers, HTTP requests, storage, SQLite and cache operations retain ownership and complete instead of being cancelled; Activity-bound resources still retire and final shutdown releases retained resources.
Validation: 229 Rust tests, full PHP SDK, protocol parity plus 5 regression tests, 277 Android JVM tests, and 4 focused Android API 36 instrumented regressions. A populated Firebase QA application also passed actual Activity.recreate(), verifying visible content, retained session and no error overlay. Exact-candidate native/native-ui first-run gates validate installed PHP/Kotlin/engine provenance. Linux CLI, Android renderer, PHP SDK archives and plugin AAR pass deterministic rebuilds and package budgets.
This patch changes Android lifecycle handling. API 26 and iOS device/Xcode tests were not rerun for this patch; no iOS implementation changed.
PAM Native 1.39.0 adds targeted Android file sharing and package availability checks, iOS custom/universal link routing and manifest configuration, an
PAM Native 1.39.0 adds targeted Android file sharing and package availability checks, iOS custom/universal link routing and manifest configuration, and fixes nested Android virtual lists while preserving recycling and visibility ownership.
Validation: Rust 229 tests; full PHP SDK; protocol parity and 5 parity tests; 277 Android JVM tests; 7 relevant Android instrumented regressions on API 36.1; exact candidate native/native-ui community first-run gates with PHP/Kotlin/engine provenance. Linux CLI, Android renderer and PHP SDK archives, and plugin AAR pass deterministic rebuild and size budgets.
iOS regression tests are included but were not executed on Linux; Xcode/device validation remains required for iOS delivery.
Android password inputs now keep their configured font family, weight and style when secure entry, keyboard type, alignment or autocorrection changes.
Android password inputs now keep their configured font family, weight and style when secure entry, keyboard type, alignment or autocorrection changes. Default password inputs no longer become monospace. No application migration is required.
Validation: Rust 226 tests, Android JVM 277 tests, PHP SDK suite and protocol parity passed. The focused real Android creation/update regression passed on API 26 and API 36, including text and selection preservation. Android renderer, PHP SDK, plugin API and Linux CLI packages were rebuilt deterministically; package budgets passed.
The iOS secure-toggle test now also verifies font preservation. iOS was reviewed on Linux and still requires execution on Xcode; no iOS product implementation changed.
Fresh community native and native-ui projects both passed init/dev/Android launch/logcat/PNG gates with candidate 1.38.1 PHP, Kotlin host and engine hashes verified.
Adds binary keyboard visibility to the PHP SDK through Keyboard::isVisible() , onVisibilityChange() and offVisibilityChange() .
Adds binary keyboard visibility to the PHP SDK through Keyboard::isVisible(), onVisibilityChange() and offVisibilityChange().
Android reports root and dialog visibility independently of keyboard avoidance and input focus, including hardware Back. Android 26–29 shares the legacy IME observer with keyboard-aware views and supports plain inputs. Foreground resume reconciles still-visible keyboards after the active lifecycle event. iOS uses main-thread keyboard notifications and the keyboard layout guide, including floating keyboards. Unsubscription and runtime shutdown release PHP listeners; inactive hosts stop legacy observation.
The protocol adds event 76 without changing existing identifiers or positional APIs. Existing keyboard avoidance behavior remains unchanged.
Validation: Rust 226 tests, Kotlin/JVM 277 tests, PHP SDK under PHP 8.5.11, protocol parity, package budgets, deterministic packages and repeated CLI/AAR builds passed. Full Android 26 instrumented suite passed 280 tests. Android 36 ran 280 tests: 279 passed initially; its sole stale navigation-bar test was corrected without changing product code, and both navigation-bar tests then passed. All five real modal/sheet keyboard and resume journeys passed. Fresh native and native-ui projects both passed the original community init/install/dev/launch/log/screenshot gate with the candidate SDK 1.38.0, confirmed by Composer and native source hashes.
Linux build: iOS source and XCTest coverage are included; Xcode compilation and physical iOS validation remain pending on the user's Mac, as agreed. See docs/ios-parity.md for the exact checklist.
System\Keyboard::isVisible(), onVisibilityChange() and
offVisibilityChange() expose binary native IME visibility on Android and
iOS, including dialog windows, sheets and hardware Back without input blur.
Native animation frames stay on the host; PHP receives only transitions.Scroll content measures each node's minHeight / maxHeight (and minWidth / maxWidth on horizontal scrollers) like layout does. A content Column holding
minHeight / maxHeight (andminWidth / maxWidth on horizontal scrollers) like layout does. AminHeight: 52 whose content was shorterSystem\ViewCapture::capture() (new, Android and iOS): renders a mounted view found by its nativeRef , with its subtree, into a private PNG or JPEG ( I
System\ViewCapture::capture() (new, Android and iOS): renders a mountednativeRef, with its subtree, into a private PNG or JPEGImageCaptureFormat), pixelRatio output pixels per point (each sideCapturedImage (file, width, height). Theopacity: 0) captures as it would look on screen — ReactgestureNativeTransform pan: the translation follows the finger under aView.getMatrix(), iOSlayer.affineTransform()); without transformed ancestors nothing changes.Notification actions for every app (found porting Zé Chat's notification "Responder" and collaboration invites):
Notification actions for every app (found porting Zé Chat's notification
"Responder" and collaboration invites):
PushRenderingRule::reply(..., hideWhen: ['can_reply' => '0']) leaves thePushRenderingRule::replyFailures(ReplyFailures): the reply is sent first;message with serverMessage), an optional retry buttondraftField. NotificationAction::$failureShown tells PHP not to{action_id}: a positive integer unique per action (milliseconds × 1000 +{action_id} and {uuid} keep their valuesPushRenderingRule::where($field, $value) and requires(...$fields) (present,PushRenderingRule::action($id, $label, ActionEndpoint, dismiss:):NotificationActionType::Button withNotificationAction::$action.PushRenderingRule::category($id, withoutReply:) registers the APNsUNTextInputNotificationAction),PamPushNotifications.didReceive(response:); failed replies stay as aPamTextLayout).Text / Span leaf no longer trims the spaces of{{ ' · '.$pronouns }} kept its separator only through<If> workaround); only the template's own whitespace at the edges isRefreshControl adopts the flex item sizing of its scroll contentflexGrow, flexShrink, flexBasis, minHeight, alignSelf) unless itrefreshControl is a prop of the ScrollView, whoseflex: 1 fills the screen, so a wrapper no longer needs its own flexGrow.ScrollView: the scrollable extent is the engine frame of theColumn has no view, sosafeBottom + 20 above the navigation bar) could never be scrolled intoAndroid Location : current() , watch() and the new lastKnown() go through the Google Play Services fused provider ( FusedLocationProviderClient ) when
Location: current(), watch() and the new lastKnown() goFusedLocationProviderClient)locationProvider: 'playServices'. The platform LocationManager failed withhighAccuracy picksPRIORITY_HIGH_ACCURACY or PRIORITY_BALANCED_POWER_ACCURACY, and a fusedlastLocation at most maximumAgeMs old answers without a new request.LocationManager path is unchanged. The renderercom.google.android.gms:play-services-location:21.4.0.Location::lastKnown(Closure $callback, ?Closure $failure = null): the lastlastLocation, then the newestLocationManager provider fix; iOS CLLocationManager.location) withoutLocationError::Unavailable when there is none.Location::servicesEnabled(Closure(bool): void);Location::requestServices(Closure(LocationServicesResult): void), which onSettingsClient) andLocationServicesResult::Enabled (1) or Denied (2), orUnavailable (3) when no dialog is possible (no Play Services, no activity,Location::openSettings(?Closure(bool): void $completed = null)ACTION_LOCATION_SOURCE_SETTINGS; iOS the app's Settings page)."<code>: <detail>" with codepermission, disabled, unavailable or timeout. $failure callbacksLocationError::fromFailure(string): LocationErrorLocationError::detail() strips the code. Location switched off is nowdisabled on both platforms (iOS used to report it as a denied permission).Modal/BottomSheet: a closed modal keeps its Dialog mounted andDialog.hide()), and once the activity was stopped and restarted byLocation::requestServices, a share sheet, the camera) Android 12 showedFLAG_NOT_TOUCHABLE and FLAG_NOT_FOCUSABLE, cleared beforeDialog.isShowing true after hide(), so a reopened modal was never shownonDismiss twice.LocationModule.swift (uncompiled; Mac checklist indocs/ios-parity.md).Location: current(), watch() and the new lastKnown() use the
Google Play Services fused provider (FusedLocationProviderClient,
com.google.android.gms:play-services-location:21.4.0) whenever Google Play
Services is available, like React Native's locationProvider: 'playServices'; highAccuracy picks PRIORITY_HIGH_ACCURACY or
PRIORITY_BALANCED_POWER_ACCURACY and a fused lastLocation at most
maximumAgeMs old answers without a new request. Without Play Services the
platform LocationManager path is unchanged.Location::lastKnown(Closure $callback, ?Closure $failure = null): the last
position the platform holds (fused lastLocation, then the newest
LocationManager provider fix; iOS CLLocationManager.location) without
starting GPS; fails with LocationError::Unavailable when there is none.Location::servicesEnabled(Closure(bool): void),
Location::requestServices(Closure(LocationServicesResult): void) (Android:
Play Services' "turn on location" dialog through SettingsClient, resolved
from the activity result; LocationServicesResult Enabled = 1, Denied = 2,
Unavailable = 3, where Unavailable means no dialog is possible and the app
should offer the settings screen) and
Location::openSettings(?Closure(bool): void $completed = null) (Android
ACTION_LOCATION_SOURCE_SETTINGS, iOS the app's Settings page)."<code>: <detail>"
with code permission, disabled, unavailable or timeout; the
$failure callbacks still receive the string and
LocationError::fromFailure(string): LocationError (Permission = 1,
Disabled = 2, Unavailable = 3, Timeout = 4) gives the typed reason, also for
the bare messages of older runtimes. LocationError::detail() strips the
code. A location switched off is now disabled on both platforms (Android
checked only for an enabled provider; iOS reported a .denied permission).Modal/BottomSheet: a closed modal keeps its Dialog mounted and
hidden (Dialog.hide()), and once the activity was stopped and restarted by
another activity (Play Services' "turn on location" dialog from
Location::requestServices, a share sheet, the camera) Android 12 showed
the hidden window's surface again as a fill-parent input target: no touch
reached the screen below until the user left it with Back. A hidden modal
window is now FLAG_NOT_TOUCHABLE and FLAG_NOT_FOCUSABLE, cleared before
the same mounted modal is shown again. The host also tells a hidden Dialog
from a presented one by its decor visibility: older platforms (API 26) keep
Dialog.isShowing true after hide(), so a reopened modal was never shown
again and a close notified onDismiss twice.Android BottomSheet : the edge-to-edge sheet window no longer enforces navigation bar contrast. On Android 10–14 with three-button navigation the syst
BottomSheet: the edge-to-edge sheet window no longer enforcesnavigationBarTranslucent full-screen modals keep the scrim like RN Modal.MediaPlayer with preloadSeconds > 0: HLS (.m3u8) sources play..m3u8 failed (ClassNotFoundException: androidx.media3.exoplayer.hls.HlsMediaSource$Factory) where the platformpreloadSeconds) plays the same stream. The renderer now depends onandroidx.media3:media3-exoplayer-hls:1.10.1 (same Media3 version), so HLSSwitch: drawn with React Native's (AppCompat SwitchCompat)ReactSwitch. The thumbthumbColor), and itsSwitchCompat reference test now matchesRenderer parity with React Native found while porting Zé Chat to PAM.
Renderer parity with React Native found while porting Zé Chat to PAM.
top/right/bottom/left of aposition: absolute child are measured from the parent's padding boxtop: 0; right: 0padding dp too low and to the left.TextLayoutManager (the layout is built atusedRect).opacity: a View/Pressable fades its subtree like React NativehasOverlappingRendering() is false, so the fill and then eachneedsOffscreenAlphaCompositing attribute / Element::needsOffscreenAlphaCompositing()Switch: AppCompat geometry of React Native's SwitchCompat — aSwitch stretched the old track drawable to the full 20 dp height.BottomSheet: the sheet window is always edge to edge, like theSafeAreaView inside it pads the navigation bar (the engine's surfacetransition / animate back to the default instead of snapping;transition: transform survives a class removed and re-added within oneopacity.MediaPlayer::preloadSeconds() / preloadSeconds="12" is the forwardAVPlayerItem.preferredForwardBufferDuration; AndroidDefaultLoadControlMediaPlayer has noMediaPlayer. Addsandroidx.media3:media3-exoplayer:1.10.1 (and Guava) to the Android host.PamRuntime(...) with the default installModules = trueinit block that locks it; since 1.29.0). A runtimephp_embed_init … php_embed_shutdown) holds a process-wideTrace.isEnabled() on API 26–28.Files::download() / Files::downloadWithProgress() without request headers now send {} instead of [] . Android ( JSONObject ) and iOS ( [String: String
Files::download() / Files::downloadWithProgress() without request{} instead of []. Android (JSONObject) and iOS[String: String]) rejected the empty JSON array, so every header-lessLocation::watch() / Location::clearWatch() : continuous position updates like React Native's watchPosition , with a distance filter and (Android) a mi
Location::watch() / Location::clearWatch(): continuous position updateswatchPosition, with a distance filter and (Android) aSensors::watch(). Android registers one LocationListener per watch on theCLLocationManager per watchdistanceFilter. A watch cleared before the platform answers stops theShare::files() takes an optional text shared beside the files (AndroidEXTRA_TEXT, iOS an extra activity item), so a picture goes out with itsShare/shareLocalFileWithText).BottomSheetKeyboardBehavior::Contain (4, template keyboardBehavior="contain"):KeyboardAvoidingView or aScrollView inside it lifts a bottom composer above the IMEadjustResize and aadjustNothing for that window; iOSAndroid Modal: a tap on the modal's content no longer counts as a backdrop tap when its layout-only wrapper was flattened into several sibling views (
Column holding a dismiss Pressable and anrequestClose, the modal unmounted first and the row's own press was lost.Gestures: gestureNativeFocalZoom="true" ( GestureDetector::nativeTransform(focalZoom: true) , property 526) makes a native-transform pinch keep the co
gestureNativeFocalZoom="true" (GestureDetector::nativeTransform(focalZoom: true),nativeScale/nativeTranslationX/Y report the applied values as before.Files::pick()/Files::pickMany() for images, videos or both openreact-native-image-picker. Other types, an explicit MIME type and devicesFiles::pickMany() accepts failure and maximumBytes (per file, 1 byte toFiles::pick(): a large video no longer failsApp text scale: Accessibility::setTextScale(float $multiplier, float $maxSystemScale = 0) persists an in-app "text size" natively and every text then
Accessibility::setTextScale(float $multiplier, float $maxSystemScale = 0) persists an in-app "text size" natively and every textmultiplier * min(system font scale, maxSystemScale) fromPamTextScale, iOS Dynamic Type multiplier).Accessibility::textScale() reports the stored and applied valuesTextScale::pendingRestart()).System\Biometrics: status() (BiometricKind) and authenticate()BiometricError) over Android BiometricPrompt (Android 10+, weak orUSE_BIOMETRIC in the host manifest) and iOSStorage\SecureStorage: get/set/delete of small secrets (64 KiB) inWhenUnlockedThisDeviceOnly) on iOS.Screen::claim(string $owner) / release() / claimed(): named secure-modeFLAG_SECURE.Commits between frames: a batch that builds something (32 mutations or more: a page of older chat rows, a reel's chrome) and any batch while a virtual
beforeWaiting observer ordered afterActivityIndicator: the spinner is a plain View drawing the sameProgressBar, whose constructor loaded theTextView taken for a new list cell no longersetText defers to the singleRuntimeFrameMetrics.stats) are read from the engine onbatches/decodeNs/mountNs per commit without them; debug builds keep theLayout: aspect-ratio follows Yoga's rules with min/max constraints on both axes. In a flex container the main size comes from the cross size (the auth
aspect-ratio follows Yoga's rules with min/max constraints on bothwidth: 100%; max-height: 100%; aspect-ratio stage now narrows, keeping its ratio, whenYGAspectRatioTest reference cases.Modal: the navigation bar follows the app's light/dark appearancenavigationBarTranslucent orstatusBarTranslucent) modal gets RN's transparent, system-scrimmed barnavigationBarHidden hides it. Re-applied after each window configuration.StatusBar: barStyle (light-content/dark-content), hidden andanimated now drive the status bar like React Native. The activeStatusBar nodes (visible route, open or opening modals) stack in mountpreferredStatusBarStyle,prefersStatusBarHidden and preferredStatusBarUpdateAnimation, and eachsetNeedsStatusBarAppearanceUpdate() (inside an animationanimated). With UIViewControllerBasedStatusBarAppearance NO thePamStatusBarTests and thedocs/ios-parity.md must pass on a Mac.Android Modal : the StatusBar declared by a modal's content (or the screen's, for a modal without one) now reaches the modal's own window. A Dialog cr
Modal: the StatusBar declared by a modal's content (or theenableEdgeToEdge) reset its icons to the appstatusBarTranslucent modal keeps its transparent bar.Android VirtualizedList : a node of a mounted cell whose index changes under the same parent (a conditional sibling inserted or removed before it) kee
VirtualizedList: a node of a mounted cell whose index changesappearance.firstFrame ( "php" default, "window" ): with "window" the Android activity draws its themed window at once instead of holding the launch sc
appearance.firstFrame ("php" default, "window"): with "window"manifest.sha256 beside the pack) boots from that listingsrc/ or reading and fingerprinting each componentopcache.validate_timestamps=0 outside debug builds, which hot reload inVirtualizedList: history prepended above the rows (also when aPamParseCache; iOS: drag configs).ActivityIndicator no longer inflates the theme'sKeyboardAvoidingView works inside Modal and BottomSheet surfaces. On Android a modal is its own Dialog window: the activity window never receives that
KeyboardAvoidingView works inside Modal and BottomSheet surfaces.Dialog window: the activity window neverWindowInsetsAnimation, and noEngine::set_surface_keyboard_inset,pam_native_engine_set_surface_keyboard_inset). The resize (RNheight) and padding behaviors of a KAV inside a modal are laid out byrelativeKeyboardHeight,keyboardVerticalOffset): the content box shrinks, so flexiblepan KAVs inside a modal translate natively against the dialogBottomSheet keeps lifting itself and itsresize/padding/position KAVs inside aheight (= resize)position (= pan).Android: appending a page to a VirtualizedList (or raising the adaptive prefetch distance during a fling) no longer lays out and binds the whole prefe
VirtualizedList (or raising the adaptiveMediaLibrary::assets() and albums() sort through the SQL sortdate_added DESC, date_modified DESC, _id DESC). MediaProvider oncreationDate descending).Keyed VirtualizedList sections for tabs over one list: rows set listSection ( Element::listSection() ) and the list activeSection ( VirtualizedList::a
VirtualizedList sections for tabs over one list: rows setlistSection (Element::listSection()) and the list activeSectionVirtualizedList::activeSection()). Unsectioned rows (header, sticky tabListSection (524) and ListActiveSection (525) propertymount-scenarios adds chat-details tabs over oneVirtualizedList (header, sticky rail, 40 rows with a photo per tab,details) or with keyed sections (details-keep), with tap-to-commit andAndroid images decode at the display size: a source larger than its view is subsampled and then scaled in the same BitmapFactory pass to the smallest
BitmapFactory pass to theresizeMethod auto/resize),repeat) images only subsample; scale/none are unchanged.Bitmap.Config.HARDWARE on API 28+ (GPU memoryRGB_565 on API 26-27. Inline data: glyphs andARGB_8888. Software canvases (shared-elementActivityManager.memoryClass (1/8, 1/16 on low-RAM devices, 8-64 MiB)Image hidden by an ancestor (a coveredImageView (one ancestor re-measure per arriving photo), eachPamCommit.mutations, PamCommit.lists and PamCommit.layout traceasset://, pam-file:// and file://preparingForDisplay(). The encoded media memory cache (1/32 of RAM,Android lint ( lintDebug , warnings as errors) passes with zero findings.
lintDebug, warnings as errors) passes with zero findings.PamRuntime holds its Activity context onlydetach,PamRuntimeHostPamNotificationCredentials.replace validates and seals everyPamList.layout trace section is always closed, also whenWrongConstant on TextView.breakStrategy (Layout and LineBreakerUnusedResources for the CLI-managed splash drawables.cargo clippy --all-targets -D warnings is clean on the toolchain inif in appearance.rs, app_icon.rs and mobile.rs;double_ended_iterator_last in layout.rs). No behavior change.Android: a hidden route mounted outside a Choreographer frame (a direct commit, not an engine batch) is laid out on the frame after the one that lays
PamNavigationHost mounts a route straight through its
route controller and restores its position with
detachViewFromParent/attachViewToParent. A new screen enters the window
once instead of being attached, detached for its fragment and moved back
(three attaches and two detaches of the whole subtree).onGestureSettle after
onGestureEnd, never before it.TYPE_TEXT_FLAG_NO_SUGGESTIONS); the IME composed over
text the formatter rewrites on every keystroke. iOS: formatted fields turn
autocorrection and spell checking off.backdrop-filter container no longer redraws on every
frame of an idle screen. It re-records what is behind it only in frames
where something in the window changed; before, its own invalidation
scheduled the next frame forever (continuous rendering, and a main thread
that never went idle, which hung waitForIdleSync in tests).CADisplayLink (which retains
its target) runs only while the overlay is in a window, so a removed overlay
is released instead of ticking forever; showing it twice no longer adds a
second display link.testReducedMotionDragSettleIsReportedAfterTheRelease and
testVisibleDevToolsOverlayIsReleasedAfterLeavingItsWindow; validate on a
Mac. New Android instrumented tests
reducedMotionDragReportsItsSettleAfterTheEnd and
backdropFilterRedrawsOnlyWhenTheWindowChanges.awaitFrames) instead of waitForIdleSync/sleeps,
tests that observe motion in flight enable animations through
PamAnimationsEnabledRule, window captures wait for a stable composited
frame, the layout-origin test expects edge-snapped sizes (1 px at density
2.75), the status-bar and transition-layer tests follow the 1.25.0
transition timing, the double-tap test dispatches both taps in one main
thread message, the controlled-input echo test types into the field, the
rapid formatted input test waits until the IME serves the focused field
before its key burst, and the DevTools test no longer waits for an idle
main thread (its snapshot checks use JUnit instead of Kotlin assert, a
no-op on Android). The reload and crypto bridge tests no longer read the
PHP report list while the runtime thread appends to it (a
ConcurrentModificationException).Android device-gallery images (content://media/... photos and videos, including the Files collection MediaLibrary::assets() pages) up to 640 px load f
content://media/... photos and videos,
including the Files collection MediaLibrary::assets() pages) up to 640 px
load from the platform thumbnail cache (ContentResolver.loadThumbnail)
and are downscaled to cover the cell, instead of reading the whole file
into the heap and decoding it. Videos show a frame instead of failing to
decode after reading up to 16 MiB. Natural size events still report the
MediaStore width and height. Larger views and other sources keep the
regular decode.ph:// photo-library sources of video assets draw their poster frame
(previously an image error), matching Android.VirtualizedList/VirtualGrid cells include their root's margins, like React Native/Yoga: a content-sized cell's slot (row height, or column width in a
height (width horizontally) stays
the root's own height and the margins are added around it; rowHeight of
a horizontal list stays the slot extent. Applies to grid rows (the tallest
margin box) and fullSpan cells. Before, the margins were dropped from the
slot and the root sat at its top-left corner.ScrollView (and sticky virtual list cells on iOS)
pin and are pushed by their margin box, like React Native's sticky header
wrapper: a pinned header keeps its top margin above it.Navigator::prewarm($route, $params) mounts a screen ahead of navigation, hidden under the current one; a following push()/navigate() with the same rou
Navigator::prewarm($route, $params) mounts a screen ahead of navigation,
hidden under the current one; a following push()/navigate() with the
same route and params reuses it (same element, views and first layout), so
the transition starts on the next frame. One prewarmed screen is kept; it is
released after 4 s unused or by any other navigation. isPrewarmed(),
cancelPrewarm() and the static Navigator::isPrewarming() (true while a
prewarmed screen renders, so mount() can defer focus-only work to
navigationFocused()) complete the API. Call it from a row's on:pressIn.detachViewFromParent/attachViewToParent instead of
leaving the window, so a press in progress on the Inbox is no longer
cancelled and kept-alive routes keep their views and list layout.!isShown) creates its cells within 5 ms
per frame and finishes them on the following frames (10 ms once shown);
cell extents are laid out at once. The first layout after a commit starts
at initialScrollIndex instead of binding position 0 and scrolling a frame
later. A list resting at its start whose rows all fit is no longer treated
as "at its end" when its viewport shrinks (an Inbox banner no longer jumps
the list to its last rows).PamNavigationHost.reorderRoute
and PamRenderer.move reorder routes without removeFromSuperview, hidden
PamVirtualListViews materialize visible cells within 5 ms per frame, and
the outgoing route is rasterized during the transition. XCTest
testReorderingAPrewarmedRouteKeepsItInTheWindow; validate on a Mac.reorderingAPrewarmedRouteKeepsItAttachedAndItsLayout,
hiddenRouteIsNotLaidOutInTheFrameThatMountsIt); see
migration notes.Source commit: a3285bb99224c0b31af5490cc9602edbc1a3e098 ( [skip ci] ).
Source commit: a3285bb99224c0b31af5490cc9602edbc1a3e098 ([skip ci]).
PAM_NATIVE_FRAME_GC=0 keeps PHP's own scheduling, a number sets theuse function imports) andElement exposes its encoding fields as read-only public propertieskind, properties, events, children, elementKey, domIdentity,identitySlot, reusable); TreeEncoder::frameNodes() returns the lastiOS: PamHeldPanGestureRecognizer imports UIKit.UIGestureRecognizerSubclass , which declares the touchesBegan / touchesMoved / reset overrides it uses;
PamHeldPanGestureRecognizer imports UIKit.UIGestureRecognizerSubclass,touchesBegan/touchesMoved/reset overrides it uses;Notification action endpoints authenticate per account while the app is killed: ActionEndpoint::bearerFromCredential('user_id', 'recipient_user_id') r
ActionEndpoint::bearerFromCredential('user_id', 'recipient_user_id')Pam\Native\Notifications\NotificationCredentials storeset, remove, sync, clear).NotificationAction::$credentialMissing reports it. Credentials resolve onlySource commit: 3364058fe27eace31400965a9a1b2172e0075762 ( [skip ci] ).
Source commit: 3364058fe27eace31400965a9a1b2172e0075762 ([skip ci]).
Accepted after native regression, community project and application UI validation.
Android scroll views consume contentOffsetX/contentOffsetY requests once
each requested position is reached. Later child layouts or insertions no
longer replay an initial offset after scrolling to the last page. Requests
still clamped by insufficient content remain pending until content grows.
Explicit property changes can request a new position. End anchoring, keyboard
clearance and tokenized scroll requests keep their existing contracts.
native-ui (API 26) and native (API 36) projects passed launch,Rebuild the Android host after updating. PHP remains ^8.5; numeric protocol/
ABI identifiers and third-party dependencies are unchanged. The 1.22.6 image,
reload, cache-recovery and initial-property improvements remain included.
See migration notes.
No iOS source changes are included, and UIKit execution was unavailable on
Linux. Native correctness and emulator UI tests do not measure FPS. Final app
integration is validated separately from this framework release. Validation uses direct local commands,
without GitHub Actions.
Source commit: 2aff2f3b49d3558503a1c9aee86cf97e7436c50e ( [skip ci] ).
Source commit: 2aff2f3b49d3558503a1c9aee86cf97e7436c50e ([skip ci]).
The final V3 source passed the release gates and integrated Android cache-recovery QA.
ImageLoadEvent, ImageErrorEvent and ImageProgressEvent handlerscanOpenUrl result. Itsnative and native-ui projects passed first launch, edit/reload/The accepted initial-properties A/B kept all 157 PAM assets byte-identical.
The largest mount CPU interval changed from 21.020 to 18.609 ms, the largest
Recycler layout CPU interval from 44.064 to 39.893 ms, and its eleven binds
from 29.714 to 27.976 ms. The total observed mount CPU increased from 27.453
to 37.593 ms; this is evidence for reduced work in the selected intervals,
not a reduction in every opening cost.
Untraced steady scroll changed from 0/417 frames classified as jank (p95 10 ms)
to 1/420 (p95 11 ms), with GPU median/p95 at 4/5 ms in both. Cold p95 changed
from 133 to 105 ms while jank changed from 10/16 to 12/16 frames. A single pair,
shader work and scheduling limit attribution. Cold opening has not achieved
the 60 FPS target, and these samples do not establish universal FPS or
complete application parity.
The image-event application regression reproduced the old TypeError and
passed the two compiled editor/crop consumers on the candidate. A candidate
V1 device session also exported edited photos and confirmed one remote post
with HTTP 201. The final V3 APK then recovered an intentionally empty Feed
class on Android: 0 bytes became the original 22,665 bytes with the exact
original SHA-256, and Feed rendered after process restart without clearing
application data. Backend
media processing remains separate from SDK correctness and release acceptance.
Update the SDK, rebuild/precompile the application bundle and rebuild the
native host. PHP remains ^8.5; third-party dependencies and numeric protocol/
ABI identifiers are unchanged. Existing 1.22.5 list and zoom fixes remain
included. See the migration guide.
Validation uses direct local commands without GitHub Actions. The iOS bridge
implements the same request-scoped callback mapping, but iOS execution was
unavailable on the Linux host. Cache size recovery does not detect arbitrary
same-size corruption or rebuild a damaged source pack. The device cache recovery evidence and source hashes are recorded in the release manifest.
ImageLoadEvent, ImageErrorEvent or
ImageProgressEvent receive decoded event objects instead of wire strings.
Direct handlers, explicit event arguments and generated/interpreted template
expressions share the existing decoder. String, untyped and zero-argument
handlers retain their contracts; forwarded event objects retain identity.Source commit: 6a333fd4122adb9598c69ef9fe3f852ebf70ba04 ( [skip ci] ).
Source commit: 6a333fd4122adb9598c69ef9fe3f852ebf70ba04 ([skip ci]).
GestureEvent::nativeScale, nativeTranslationX andnativeTranslationY report the applied transform for committing interruptednative and native-ui projects passed installation, first launch,Rebuild the Android host after updating. No numeric protocol identifiers or
third-party dependency requirements change. See
the migration guide.
Validation used direct local commands without GitHub Actions. Three UIKit
regression tests are included, but Swift/UIKit execution was unavailable on the
Linux host. The iOS handoff covers CSS/program transforms on the shared photo
surface; a TapEffect owned by an ancestor and animating a child is outside this
coverage. End-to-end APNs/FCM delivery was not tested. Initial text/background
batching and rejected drawing experiments are not included in this release.
GestureEvent::nativeScale, nativeTranslationX and
nativeTranslationY report the applied native transform; existing relative
gesture deltas and positional constructor parameters remain compatible.