React Native code push by HotCodePush

@hotcodepush/react-native-code-push is the React Native module that delivers over-the-air (OTA) updates to your app. Ship a JavaScript fix with one command, reach every installed app within seconds, and roll it back from the console if something goes wrong. No store review, no new build. Learn more at hotcodepush.com/react-native-code-push.

Features

• ⚡️ One command to release. npx hotcodepush release create --platform ios bundles, signs and publishes.
• 📺 Channels. Staging, beta and production, each with its own release log, and promotion between them.
• 🚀 Staged rollouts. Start at 5 percent, widen in steps, and let the automatic pause stop a release that fails on devices.
• 🛟 Rollback. One command or one click sends every device back to the release before.
• 🔁 Delta updates. A device downloads what changed, built on the platform from the bundle it runs.
• 🔒 Code signing. The app runs only bundles signed with your key, which never leaves your machine or your CI.
• 🎯 Conditions. Target a release by binary version, OS version, device attributes or a list of devices.
• 🖥️ Console, CLI and GitHub Action. Watch devices arrive on a release in the console, release from the terminal, or from a workflow step.
• 🤖 Built for agents. An MCP server and agent skills let Claude Code or Cursor set up, release and debug for you.
• 🌐 Open source. The module, the CLI, the clients and the Action are MIT licensed.

Compatibility

| Module | React Native | iOS | Android | | ------ | -------------------------------- | -------------- | ---------------------- | | 0.x | 0.82 and later, New Architecture | 15.1 and later | 7.0 (API 24) and later |

Demo

react-native-code-push-demo is a React Native app with the module wired in, built on both platforms and released through the GitHub Action on every merge.

Guides

• Quickstart, the first release end to end
• Migrate from CodePush, with the mapping of every command and option
• Release from CI, GitHub Actions, GitLab, Bitrise, Codemagic and more

Installation

AI-assisted setup (recommended)

Paste this prompt into the agent or assistant you use:

Set up HotCodePush OTA updates in this project, following https://hotcodepush.com/docs/quickstart.md. If you can run commands, install the agent skills with `npx skills add hotcodepush-team/skills`, then run hotcodepush-init and hotcodepush-release. If you cannot run commands, read that page and give me the steps to do it myself.

An agent that runs commands installs the module, creates the app and the channel, and ships the first update. An assistant without a shell reads the quickstart and hands you the steps. Agent skills explains what the agent does.

Set up with the CLI

npx hotcodepush init

init signs you in, picks or creates the app, installs the module, writes hotcodepush.json, wires both native projects and offers a signing key. Build the app once in release, an Xcode archive or a Gradle release variant, so the store build registers itself. Then change something and ship it:

npx hotcodepush release create --platform ios
npx hotcodepush release create --platform android

The installed app downloads the release at its next start and runs it from the start after that. A debug build loads its JavaScript from Metro, so OTA updates are off there.

Prefer to wire it yourself? The installation guide has the five steps by hand: the package and the pod, hotcodepush.json, the two host edits, the build step and the check with doctor.

Usage

Sync and read the result

With the default checkStrategy of auto, the SDK checks on start, on resume and in the foreground, and sync() runs one cycle on demand. Applying an update reloads the JavaScript without restarting the app.

import { HotCodePush } from '@hotcodepush/react-native-code-push';

const result = await HotCodePush.sync();
if (result.status === 'downloaded') {
  console.log(
    `release #${result.release.number} applies at ${result.applyStrategy}`,
  );
}

Show your users what is happening

The useUpdates() hook follows the five events and the state, so a badge, a progress bar or a restart prompt is a few lines:

import { HotCodePush, useUpdates } from '@hotcodepush/react-native-code-push';

function UpdateBanner() {
  const { downloadProgress, isSyncing, lastSync, state } = useUpdates();
  if (downloadProgress !== null) {
    return <ProgressBar value={downloadProgress} />;
  }
  if (lastSync?.status === 'downloaded') {
    return (
      <Button
        title="Restart to update"
        onPress={() => HotCodePush.applyUpdate()}
      />
    );
  }
  return (
    <Text>
      {isSyncing
        ? 'Checking…'
        : (state.currentRelease?.bundleVersion ?? 'embedded')}
    </Text>
  );
}

Decide when an update lands

Set downloadStrategy and applyStrategy to manual in hotcodepush.json, then download and apply at the moments you choose, and hold the SDK's own restarts while a flow must not be interrupted:

await HotCodePush.setRestartAllowed({ isAllowed: false });
await HotCodePush.downloadUpdate();
await HotCodePush.setRestartAllowed({ isAllowed: true });
await HotCodePush.applyUpdate();

A release that never renders is rolled back on its own, and rollbackUpdate() does the same on your call, so nothing above is needed for safety.

Target the right devices

A release with an --attribute plan=enterprise condition reaches the devices that carry the attribute, and a beta switch in your settings screen is one call. The channel sticks until the app clears it with setChannel(null):

await HotCodePush.setAttributes({
  attributes: { plan: 'enterprise', userId: '42' },
});
await HotCodePush.setChannel({ name: 'beta' });

See why a device did not update

The debug screen shows the device id, the channel, the binary and the result of the last check, the first stop for a device that did not update. getState() gives the same to your own diagnostics:

await HotCodePush.showDebugScreen();
const { currentRelease, lastCheck } = await HotCodePush.getState();

Documentation

See hotcodepush.com/docs/sdks/react-native for the configuration, methods, events, types and reasons.

Development

See CLAUDE.md for the layout and the commands, and CONTRIBUTING.md for the rules of a change. The iOS code compiles only inside an app, so CI builds the demo app with the module from the commit. The native cores live in core-ios and core-android.

License

See LICENSE. An app that ships the module also ships the native cores' third-party code: FreeBSD's bspatch (BSD 2-clause) on both platforms and bzip2 1.0.8 on Android. Reproduce the notices from core-ios and core-android in your app's distribution.