React Native's New Architecture is mandatory from version 0.82, replacing the legacy bridge with JSI, TurboModules, and Fabric. OTA update delivery itself is unaffected by these changes — bundles are still compiled and pushed the same way. However, teams must verify several things before their first post-migration OTA push: CodePush SDK compatibility, native module bridge assumptions in JavaScript code, Hermes engine compatibility (stricter than JavaScriptCore), and staging environment parity. Key mistakes to avoid include assuming OTA tooling migrates automatically, skipping OTA delivery testing in staging, pushing New Architecture-specific JS bundles during the migration window when users may still be on the old native binary, and updating rollback targets before confirming production stability. Hermes bytecode is tied to the Hermes version in the native binary, so OTA bundles must be compiled against the same React Native/Hermes version as the production binary.
Table of contents
What the New Architecture actually changedWhat stayed the same for OTA updatesWhat you do need to checkThe migration checklist for OTA teamsWhat teams are getting wrong during migrationThe Hermes engine: what OTA teams specifically need to knowSummaryFrequently Asked QuestionsRelated reading2.4K Impressions1 Comment