feat(ios): add dynamic Live Activities - #239
Merged
Merged
Conversation
Restore VoltraDynamicLiveActivityRenderCache (removed to fix hot-reload staleness) with a revision field on the cache Key. The token is the debug cache file's modification time in DEBUG (rewritten on every hot reload) and a constant in release, so a dev reload busts the cache while production keeps the shared per-update evaluation across Dynamic Island regions.
Metro calls global.__accept for every accepted patch, sometimes several times per save. Each dev hook (enableWidgetHotReload, useUpdateOnHMR on both platforms, plus enableDynamicLiveActivityHotReload on iOS) wrapped __accept itself, so N hooks meant N wrappers, N side effects per patch, and teardown order that could clobber another hook's wrapper. Extract a single FastRefreshHub in @use-voltra/core that wraps __accept once and debounces, re-exported through the @use-voltra/ios and @use-voltra/android package surfaces. All five hooks now subscribe via onPatch, so a burst of __accept calls collapses into one reload. Adds Node tests on both platforms.
V3RON
marked this pull request as ready for review
August 10, 2026 10:43
The changeset described this branch as three internal fixes, but it actually ships the whole Dynamic Live Activities feature (bundled rendering definitions, dedicated Metro pipeline, new ios-client APIs, and plugin config). Bump affected packages as minor and describe the capability instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this?
This adds experimental Dynamic Live Activities for iOS. Applications bundle named Live Activity definitions with the installed release and send only JSON-compatible props through ActivityKit, while the existing server-rendered Live Activity engine and payload format remain supported.
How does it work?
The Expo plugin validates declared definitions and generates a distinct ActivityKit attributes type, configuration, catalog registration, and bundle entry for each definition. Metro serves definitions from a dedicated development route and produces isolated release assets. The shared native runtime renders complete Live Activity variants on device, provides explicit dynamic start and update APIs, preserves unified lifecycle behavior, validates ActivityKit payload limits, and reports recoverable render failures through an App Group-backed event path.
Why is this useful?
Dynamic updates carry only application props instead of a fully rendered UI payload, reducing payload size while retaining compatibility with active legacy Live Activities and older releases. Per-definition ActivityKit types let unsupported releases reject remote starts safely, and capability discovery helps servers route the correct payload format.