OTA Updates: Ship JS Fixes Without App Store Review
Over-the-Air (OTA) updates let you ship JavaScript, styling, and image changes directly to users, bypassing app store review. Use it to fix JS bugs or tweak UI between releases. The footgun: you can't update native code or change permissions this way.
Why it exists
App store review cycles are slow. A small UI bug or typo that would be a quick fix on the web could take days to deploy to a mobile app. Over-the-Air (OTA) updates solve this by allowing developers to push changes to the non-native parts of an app directly to users, bypassing the store.
The mental model
Think of your React Native app as a native shell that loads a JavaScript bundle. An OTA update is like shipping a new version of that JS bundle without rebuilding the entire shell. The native code on the user's device remains unchanged, but it loads new logic, UI, and assets on its next launch. It's a way to trade the ability to change native code for deployment speed.
How it works
When you build your app with a library like expo-updates, the app is configured to check a specific URL for new bundles. Using a service like Expo Application Services (EAS), you run a command like eas update. This bundles your current JavaScript and assets and uploads them to EAS's cloud service. The next time a user opens your app, it can check for an update, download the new bundle in the background, and apply it on the subsequent launch.
When to use it
Use OTA updates for rapid fixes and improvements that don't touch native code. This includes fixing bugs in your JavaScript logic, correcting typos, updating translations, changing UI styling or screen layouts, and pushing new images or other assets. It's also great for rolling out features to a small percentage of users or for internal testing before a full release.
When not to use it
Do not use OTA updates for any change that requires a new app binary. This includes changing native code or adding new native dependencies, updating app permissions (like camera or location access), or upgrading the Expo SDK version. These changes always require a full rebuild and submission to the App Store and Google Play. Attempting to bypass this is a common footgun that will lead to crashes or broken functionality.
One canonical example
A user reports a critical bug where the login button is misaligned, preventing them from logging in. The fix is a one-line style change. Instead of waiting days for an app store review, you make the change, run eas update --channel production --message "Fix login button alignment", and publish. Most users will receive the fix the next time they open the app, resolving the issue in minutes instead of days.
Interview question
Which of the following changes cannot be deployed to users using an Over-the-Air (OTA) update?
- a.Replacing an outdated image asset with a new one
- b.An update to the app's UI styling or screen layouts
- c.A new feature requiring additional device permissionsCorrect
- d.A critical bug fix in the app's JavaScript logic
Why? this is the answer
The card explicitly states that changes requiring new app permissions cannot be deployed via OTA updates and require a full app store submission. The other options describe changes to JavaScript, styling, or assets, which are precisely what OTA updates are designed to handle.
Just read this? Test yourself on what you have been reading.
Read the original → docs.expo.dev
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on react native — each one lists the topics its interview covers.
See open roles