Over-the-Air Updates for JavaScript-Only Fixes

WHAT THIS TESTS Whether you understand that React Native apps run a JavaScript bundle on top of a native shell, so JS-only fixes can be delivered without rebuilding the native binary.

A GOOD ANSWER COVERS Over-the-air updating ships a replacement JavaScript bundle and its assets to already-installed apps. Services like Expo Updates and CodePush host the new bundle; the app queries the update endpoint, downloads the patched bundle in the background, and applies it on the next cold start, or immediately if you force a reload. For a critical JS-only bug you patch the code, publish to the release channel or branch that the current production binary listens to, and users receive the fix on next launch with no store review. You scope updates by runtime version or target binary version so a bundle never lands on an incompatible native shell.

COMMON WRONG ANSWERS Claiming OTA can update native code, add a new native module, or change native permissions; those require a new store build. Believing OTA bypasses store policy for behavior changes that should go through review. Forgetting that an update applies on next launch, not necessarily instantly mid-session.

LIKELY FOLLOW-UPS How runtime versions prevent shipping a JS bundle to an incompatible native build. The tradeoff between applying on next launch versus forcing an immediate reload. Rollback strategy if the update itself is bad.

ONE CONCRETE EXAMPLE A null check is missing and the app crashes on a profile screen. You add the guard, run the publish command pointing at the production channel, and within minutes installed apps download the bundle and apply the fix on their next launch, all without an App Store or Play review cycle.