The New Default. Your hub for building smart, fast, and sustainable AI software
Table of Contents
and 5 more
React Native apps pass App Store review on the same terms as fully native apps.
The line teams cross is post-approval behavior: App Review Guideline 2.5.2 bars apps from code that "introduces or changes features or functionality of the app," which decides how far an over-the-air (OTA) JavaScript update can go before it needs a new reviewed build. That line matters more in 2026, with CodePush gone and Apple blocking updates for apps that run downloaded code.
Monterail's React Native development team handles deployment and launch as part of its projects. The Guild messaging app, built with React Native, reached the app stores with every feature planned for its first release.
Executive Summary
React Native is not a rejection risk on the App Store; changing an app's features after review is.
Apple's license permits downloaded interpreted code only when it keeps the app's primary purpose, respects OS security and creates no store for other apps, and Guideline 2.5.2 also bars downloaded code that changes features.
Google Play's Device and Network Abuse policy has an interpreter exception and no equivalent features clause. On both stores, native changes need a new binary. Teams still on CodePush must move, since Microsoft retired it on March 31, 2025.
Can React Native apps ship OTA updates without App Review?
Partly. An OTA update replaces the JavaScript bundle and assets inside an installed app, so a fix reaches users without a store submission. That speed is why the rules matter commercially, since an update that crosses Apple's line puts the next reviewed build at risk.
Section 3.3.1(B) of Apple's Developer Program License Agreement is the operative text, allowing downloaded interpreted code "only so long as such code: (a) does not change the primary purpose of the Application", with two further conditions on OS security and storefronts.
Expo's own guidance for EAS Update tells teams that changes to app behavior usually need review.
Change | Technically possible OTA? | App Store | Google Play (Device and Network Abuse policy) |
|---|---|---|---|
JavaScript bug fix, same features | Yes | DPLA 3.3.1(B) allows it if the primary purpose is unchanged; Guideline 2.5.2 and Expo's guidance make any behavior change a review risk | Likely within the interpreter exception (Google's example names webviews and browsers), if the code does not allow potential policy violations |
Styling, images, copy | Yes | Same conditions as a JS fix | Same as a JS fix |
New or changed feature in JavaScript | Yes | Guideline 2.5.2 bars downloaded code that introduces or changes features, so ship it in a reviewed build | No features clause; the same interpreter-exception condition applies |
Native code, native dependencies, permissions | No, needs a new binary | New build through App Review | Downloading dex, JAR or .so files outside Google Play is prohibited |
Skipping OTA and shipping every change as a full store release avoids this risk entirely, at the cost of waiting for review on every fix.
Is the JavaScript bundle part of what App Review approves?
Yes. A React Native app is a native binary that ships with a JavaScript bundle, and Apple's warnings measure later changes against the app's behavior "when it was initially reviewed for the App Store."
Hermes, React Native's default engine since version 0.70, compiles that JavaScript to bytecode at build time in release builds, so the code App Review sees is fixed at submission. Hermes V1 became the default in React Native 0.84.
An OTA update swaps that bundle afterward. Section 3.3.1(B) names no JavaScript engine, so its conditions apply to a Hermes bundle as to any downloaded interpreted code, and they concern what the code does.
For engineering leads, the workflow consequence is two release tracks with different gates. Native changes, permissions and new features travel on the binary track through App Review. Fixes and content go out on the OTA track, where tooling enforces the boundary: EAS Update uses runtime version policies so an update reaches only builds with compatible native code.
The business payoff is a shorter path for JavaScript-only fixes, priced against the risk that an overreaching update draws a rejection on the next submission. Our breakdown of the pros and cons of React Native covers the wider trade-offs.
Has Apple rejected React Native apps over downloaded code?
Not as a framework. Apple's notices and statements target the ability to change an app after review, regardless of the technology used.
Native hot-patching SDKs drew Apple's warnings. Apple cracked down on developers using SDKs like Rollout, and the App Review notice posted by developers using JSPatch listed dynamic method calls such as dlopen() and performSelector: alongside remote scripts that change app behavior. Apple's stated concerns were access to private frameworks and methods, future feature changes, and man-in-the-middle attacks through a hijacked remote resource.
Unused capability still counts. Apple's message to affected developers covered "linked framework" code and stated, "While you may not be using this functionality currently," the code could enable future changes. A third-party SDK inside a React Native app can trigger a rejection that the team's own code never would.
Generated code that changes the app is treated the same way. Apple blocked updates for Replit and Vibecode under Guideline 2.5.2, and an Apple spokesperson said the policy is not targeted specifically at vibe coding apps.
React Native apps remain on the store at scale. The React Native showcase lists Facebook, Microsoft Office, Microsoft Teams and Amazon Shopping among its iOS and Android apps. Teams building with React Native have no reason to worry about the framework itself; an audit should start with the libraries that can download and execute code.
Which App Store guidelines can reject a React Native app?
Each requirement comes from Apple's guideline text, and each example shows how a React Native project could breach it.
Guideline | Requirement | Example breach in a React Native project |
|---|---|---|
2.1(a) App Completeness | Final builds, tested on-device, with demo account details and a running back end | A login screen with no demo credentials, or a staging API switched off during review |
2.3.1(a) Hidden features | No hidden, dormant or undocumented features | Feature flags or OTA bundles that switch on functionality after approval |
2.5.1 Software requirements | Only public APIs; must run on the currently shipping OS | A third-party native module that calls a private API |
2.5.2 Downloaded code | No downloaded code that introduces or changes features | OTA updates used to launch features |
4.2 Minimum Functionality | More than a repackaged website | An app that mainly displays the company site in a WebView |
5.1.1(v) Account Sign-In | In-app account deletion if the app supports account creation | Sign-up flows built without a matching deletion flow |
Guideline 4.2 is easy to read as a framework judgment, and Apple's text gives no basis for that: it asks whether an app is "app-like" and elevated beyond a repackaged website. A React Native app rendering native components can meet that bar, and a thin WebView wrapper around a marketing site fails it, whichever framework hosts the WebView.
Teams evaluating cross-platform mobile development should treat these six guidelines as acceptance criteria for every release, the OTA ones included.
Does Google Play allow React Native OTA updates?
Likely, under conditions that differ from Apple's in emphasis. Google Play's Device and Network Abuse policy bars an app from updating itself through anything other than Google Play's update mechanism and from downloading executable code such as dex, JAR or .so files from another source.
Interpreted code is the exception. Code that runs in a virtual machine or interpreter with indirect access to Android APIs falls outside the ban, and the policy's example is JavaScript in a webview or browser.
A React Native bundle runs in Hermes, a JavaScript engine, which fits that interpreter wording on a plain reading even though Google names only webviews and browsers. Interpreted code loaded at runtime must not allow potential violations of Google Play policies.
Nothing in the Device and Network Abuse policy matches Guideline 2.5.2. Apple restricts downloaded code that changes features, while Google's policy asks whether loaded code could violate policy. A JavaScript-only feature that needs a reviewed build on iOS therefore meets no features rule on Android.
Teams that run one release process for both stores can hold Android to the stricter Apple rule and keep the two versions at feature parity.
Which tools replace CodePush for React Native OTA updates?
Expo's EAS Update is a managed option, and a fork of Microsoft's archived CodePush server is a self-hosted one. Microsoft retired CodePush together with App Center, taking its hosted OTA service for React Native apps offline.
A standalone CodePush server followed so teams could keep the workflow, but Microsoft archived that repository on May 20, 2025. It is read-only, so self-hosting means owning a fork, its security patches and its upgrades.
EAS Update changes an app's non-native pieces, such as JavaScript, styling and images. According to Expo's documentation, changes to native code or native dependencies, app permissions and Expo SDK upgrades still need a new binary through EAS Build.
Expo also states that updates must follow App Store and Play Store guidelines, both in content and in how teams use them, which makes a short check worth running before each OTA release:
Confirm the update targets the current runtime version and touches no native code.
Check that the change fixes or adjusts existing behavior and adds no feature; anything new goes to the binary track.
Make sure no dormant feature switches on, which Guideline 2.3.1(a) prohibits.
Review the bundle content against store guidelines, since Expo's documentation places responsibility for update content on the team.
What else does a React Native build need to reach the App Store?
Privacy declarations, a current toolchain and audited third-party SDKs. Each can stop a build at upload or in review, whatever its OTA setup.
Privacy manifests and required-reason APIs
Since May 1, 2024, apps uploaded to App Store Connect must declare approved reasons for Apple's listed APIs, including calls made by third-party SDKs, under Apple's upcoming requirements schedule. Apple's list of SDKs that require a privacy manifest includes Hermes, React Native's default JavaScript engine.
The friction is in aggregation: Expo's privacy manifest guide warns that Apple does not correctly parse all PrivacyInfo files included by static CocoaPods dependencies, so teams may need to restate library reasons in their own app config.
Xcode, SDK and React Native version minimums
Since April 28, 2026, uploads must be built with Xcode 26 or later against the iOS 26 SDK, and since September 9, 2026, apps must target iOS 13 or later.
React Native sets its own floor on a separate schedule. React Native 0.87 raised the minimum toolchain to Node.js 22, Android Gradle Plugin 9 and Kotlin 2.0+ and moved 0.84.x to unsupported, so a release plan has to track Apple's upload minimums and React Native's supported releases together.
Third-party SDK audits
Every native SDK in a React Native project needs checking for downloaded-code capability and privacy manifests before submission. App Review's notices cover linked frameworks, and Apple's required-reason rule covers APIs called from third-party SDKs, so the team that ships the app owns both outcomes.
Key Takeaways
Rejection risk comes from post-approval changes, third-party SDKs that can download code, and guideline basics such as in-app account deletion.
OTA updates suit JavaScript fixes and assets; Guideline 2.5.2 makes new features a review risk, and native changes need a new binary.
Microsoft retired CodePush on March 31, 2025, and its standalone server repository was archived on May 20, 2025.
Apps uploaded since May 1, 2024 must declare required-reason APIs, and Hermes appears on Apple's privacy-manifest SDK list.
Google Play exempts interpreted code from its downloaded-code ban, provided code loaded at run time does not allow potential policy violations.
How should a React Native team run releases to pass App Store review?
For a React Native product, review outcomes depend on how the release process is run, so that is where a CTO evaluating the framework, or choosing a team to build with it, should look first. How a vendor separates binary releases from OTA updates says more about review risk than which framework it prefers.
In practice, that means a binary track for anything native or new, reviewed every time, and an OTA track limited to fixes and content behind a runtime-version check. Each submission starts with an SDK inventory, and toolchain upgrades follow both Apple's and React Native's schedules.
Because none of it depends on one vendor's OTA service, a team that owns the process can swap EAS Update for a self-hosted server, or drop OTA entirely, without changing how it passes review.
Monterail built Beryl's bike-sharing app in React Native for iOS and Android, designed for hundreds of thousands of simultaneous users. If you're planning a React Native release, or want a second opinion on your OTA setup, talk to our React Native team.
React Native App Store FAQ





