When a critical bug hits a React Native production app, waiting days for App Store review is painful. Over-the-air (OTA) updates via CodePush let teams push JavaScript-layer fixes directly to users' devices in hours, bypassing store review entirely. The process covers: determining if a bug qualifies (JS-only changes), pre-configuring staging and production deployment channels, writing a tightly scoped fix, validating in staging including a rollback test, deploying to production via a staged rollout (5%→25%→100%) with crash/error monitoring, confirming resolution, and documenting the incident. Native code changes still require a full store release, but the majority of production bugs are JavaScript-layer and qualify for OTA.
Table of contents
Step 1: Determine whether the bug qualifies for an OTA fixStep 2: Have your deployment channels configured before an incident happensStep 3: Write and test the fixStep 4: Push to staging and validateStep 5: Deploy to production with a staged rolloutStep 6: Expand to 100% and confirm resolutionStep 7: Document the incident and the responseSetting up OTA capability before the next incidentFrequently Asked QuestionsRelated ReadingSort: