Skip to content

React Native compatibility ​

Our compatibility target is React Native 0.77.x through the current stable release (0.88 as of 2026-11-10). The SDK currently declares React Native 0.77+ and React 18.3.1+. A permissive version declaration does not certify untested or future releases. You do not need to upgrade a React Native 0.77.3 / React 18.3.1 app just to use PushOTA. React Native's own React-version requirements still apply to your chosen release.

The previous SDK archive declared React 19 / RN 0.78 minimums. Those requirements were too restrictive for 0.77 projects. Download the current helper from Setup guide, rerun its connect command with --install-sdk, and reinstall native dependencies. Existing signing keys and project identity are reused, including with Yarn Classic.

The helper checks installed versions before it signs in or changes configuration. Versions below these minimums stop with an actionable error. When dependencies are absent, exact stable versions in package.json can be checked; version ranges require installing dependencies first. A successful version check is not proof that native integration or a store build is complete.

Support and verification status ​

React Native linePinned consumer checkCurrent evidence
0.770.77.3 / React 18.3.1SDK + consumer type check passed locally on 2026-11-10; native acceptance must match your app and architecture
0.780.78.3 / React 19.0.0SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.790.79.7 / React 19.0.0SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.800.80.3 / React 19.1.0SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.810.81.6 / React 19.1.4SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.820.82.1 / React 19.1.1SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.830.83.10 / React 19.2.0SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.840.84.1 / React 19.2.3SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.850.85.3 / React 19.2.3SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.860.86.3 / React 19.2.3SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.870.87.1 / React 19.2.3SDK + consumer type check passed locally on 2026-11-10; full native acceptance pending
0.880.88.1 / React 19.3.0SDK + consumer type check passed locally on 2026-11-10; earlier validation-app evidence is separate from customer store acceptance
Below 0.77NoneUnsupported by the current SDK/setup helper
Newer minors, prereleases/nightliesNone until added and testedUnverified; not automatically supported

The supported product platforms are iOS and Android. Inherited Windows/tvOS code is not part of the supported product or this acceptance matrix.

The matrix tests one pinned patch per minor. Passing it does not prove every patch, architecture, engine, native module or customised app in that minor. The machine-readable matrix lives in the SDK's security-tests/react-native-matrix.json; the private repository's PR checks show actual pass/fail results. CI additionally runs the production iOS/Android filesystem, watchdog, recovery and routing guards with controlled host boundaries. A successful guard test is not a full native application build.

When React Native releases a new version ​

  1. The release-watch workflow compares published stable versions against the pinned matrix and fails visibly when a new minor or patch needs review. Dependabot opens dependency update PRs; neither process automatically declares support or merges upgrades.
  2. Review React Native release notes and upgrade requirements, update the SDK's compatibility branch, and run consumer checks plus native iOS/Android builds. Fix API/architecture differences in the SDK before widening support claims.
  3. Exercise signed immediate updates, bad-signature rejection, failed-start rollback, the ten-second watchdog, pairing, device removal and recovery on both platforms. Test the selected store-installed app through TestFlight/Play testing before promoting its OTA release.
  4. Publish a reviewed, pinned SDK release and update this table with the evidence. An SDK/native integration change requires rebuilding and distributing the native app. Existing installations keep their embedded SDK until users install that native update; OTA JavaScript cannot upgrade native React Native/SDK code.

The SDK can remain compatible with an older React Native line after upstream maintenance ends. That does not extend React Native's own security support; consult the upstream release policy.

Package managers and workspaces ​

Standalone apps support npm, pnpm and Yarn with a node_modules linker. The helper uses the declared package manager and lockfile, and rejects conflicting declarations instead of switching managers. Installed packages and the React Native CLI resolve from the app's location, including hoisted npm/Yarn workspaces and pnpm package links.

Automatic setup --install-sdk and uninstall are not supported for a nested workspace app yet: they stop before login or file changes because the workspace's shared lockfile is outside the app's uninstall receipt. Changing that shared lockfile affects sibling projects and needs workspace-aware recovery support. Yarn Plug'n'Play is also explicitly unsupported; no linker or package manager is changed automatically.

If the pinned OTA SDK is already installed and managed through your workspace's own workflow, run the dashboard setup command without --install-sdk to add the app's configuration. prepare-native and publishing support installed node_modules workspaces. Native loaders, CocoaPods and Gradle must resolve the same installed SDK location; app-local ../../node_modules paths may need adjustment in a hoisted workspace. This path does not enable automated workspace uninstall: workspace dependency and integration removal must remain part of your workspace's own reviewed workflow. Use a standalone app if automatic complete installation/removal is required.

Choose the matching native loader ​

In Setup guide → Add to your app, select the language and host already used by your project. Keep the rest of your app initialization intact.

ProjectIntegration
iOS Swift, including RN 0.77Import CodePush; return CodePush.bundleURL() from the existing release bundleURL() override.
iOS Objective-C / Objective-C++Import <CodePush/CodePush.h>; return [CodePush bundleURL] from the release bundleURL method. Keep sourceURLForBridge calling that method.
Android Kotlin, RN 0.77–0.81Override getJSBundleFile() inside the existing DefaultReactNativeHost / ReactNativeHost object.
Android Kotlin, RN 0.82+Pass jsBundleFilePath = CodePush.getJSBundleFile() to the existing getDefaultReactHost(...) call.
Android Java, ReactNativeHostOverride getJSBundleFile() inside the existing host.

For Android, also apply the SDK's android/codepush.gradle from android/app/build.gradle. With New Architecture on RN 0.77, keep bridgeless mode enabled (load(); do not pass bridgelessEnabled = false). Our native validation uses Hermes and New Architecture. Changing architecture is a native change and requires a fresh compatibility registration and build.

Migrating from Revopush or Microsoft CodePush ​

Removing the old npm package does not remove its imports or configuration. Replace the old JavaScript wrapper/imports with our generated readiness helper; use the SDK's named exports. Merge the generated Production native settings, signing public key and pairing flag. Remove the previous deployment-key entries and Android package/Gradle references. Install iOS pods through your existing workflow. Do not leave two native OTA SDKs installed together.

Call startOtaUpdates() after essential startup checks succeed. Place OtaTestingEntry on the app screen you choose. The signing private key stays outside the project.

Finish native integration, then run prepare-native with the version/build you will distribute. Build and install through TestFlight or Google Play testing before OTA testing. Pair the installation, publish a small Staging update and test update/recovery before promotion. Use --target-version when the installed testing version differs from the latest public store version.

SDK tests and simulator builds establish compatibility for the tested fixture. They do not establish that your app, its other native libraries, physical devices or store distribution have passed validation. See native compatibility protection, setup and Test devices.

Signed React Native updates. Self-hosted on your infrastructure.