Wrote up how I set up over-the-air updates with Expo’s EAS Update so JS-only fixes ship without an App Store or Play Store release. One command from the laptop and it’s live on next launch.
What’s covered:
The runtimeVersion + channel model, and why updates get silently rejected when they don’t match
Silent OTA vs an “update now” banner, and when each one is the right call
Channels vs branches (not the same thing, and mixing them up bites people)
Rollback for when the OTA fix you panic-shipped is also broken
The changes that look OTA-friendly but actually need a full rebuild
Running Expo SDK 54 / RN 0.81. Setup took about an hour. Feedback welcome.
Top comments (0)