Managing Over-the-Air JS Updates with Expo EAS Update
Learn how to use EAS Update to deploy JavaScript and asset fixes to Expo apps without store reviews, using runtimeVersion and channels for safety.
Loading…
ReadMeFeed / Community knowledge
#eas-update
Real questions. Useful conversations. Find the people who know your stack.
expoBypassing the App Store: Implementing OTA Updates with expo-updates
Learn how to use expo-updates to deploy JavaScript fixes and features instantly, bypassing the App Store review process while maintaining native stability.
EAS Update OTA Architecture for Managed Expo Apps
Architecture note for using EAS Update to deliver JavaScript and assets over the air in managed Expo apps, covering requirements, minimal design, trust boundaries, operational checks, failure modes and when to change the design.
Shipping JavaScript Fixes Without the App Store: Expo Updates and the Runtime Version Gate
Expo Updates lets you ship JavaScript fixes in minutes instead of waiting for store review — but only if you treat the runtime version as the compatibility contract it is.
Shipping a Hotfix in Minutes: A Practical Look at Expo EAS Update
EAS Update lets you push JavaScript fixes to installed Expo apps without store review. Here's how runtime versions keep OTA updates safe, a staged rollout example with rollback, and where the model breaks down.
EAS Update Published Successfully but Users Still Run the Old Bundle: A Diagnostic Guide
eas update succeeded but users still run the old bundle? Diagnose channel/branch mapping, runtime version mismatches, cold-start timing, and crash rollbacks — and know when OTA can't help.
Expo OTA Updates with EAS Update: Runtime Versioning, Rollback, and the Native Boundary
OTA updates let you fix shipped JavaScript without a store review, but only inside the native boundary. How runtime versioning and rollback actually work.
expo-updates runtime and EAS Update service: how should rollback recovery be verified on real devices?
Context Our app ships with the expo-updates runtime embedded in the binary and receives OTA bundles from the EAS Update service via channel/branch mapping. After a bad release, we plan to roll back by repointing the channel to an older branch (or republishing a previous update). The interoperability gap is at the trust boundary: the client decides which publ
Runtime version mismatch in EAS Update native builds
JS Bundle and Native Runtime Incompatibility When utilizing Expo Application Services (EAS) Update for over-the-air (OTA) deployments, the runtimeVersion defined in app.json serves as the primary guardrail. This mechanism ensures that JavaScript bundles are only delivered to clients with a compatible native binary. A critical constraint exists where OTA upda