Expo

@hotcodepush/expo-ota-updates delivers over-the-air (OTA) updates to an Expo app. It is the React Native SDK with a config plugin that wires it into the native projects at npx expo prebuild. The package re-exports the module's API, so an app imports from the Expo package alone. The short version is the site's Expo OTA updates page.

It supports Expo SDK 55 to 58 in a build of your own, a development build or a release build. Expo Go carries no native module of the SDK. The React Native and OS floors of each SDK are on Supported versions.

Set up in one commandCopy Anchor Link

Let your coding agent do it: install the HotCodePush skills and paste the prompt on Installation. Agent skills explains what the agent does.

npx skills add hotcodepush-team/skills

Or run the CLI yourself. init installs the package, writes hotcodepush.json, adds the plugin entry to the app config and signs you in:

npx hotcodepush init

Use itCopy Anchor Link

import { HotCodePush } from '@hotcodepush/expo-ota-updates';

export async function syncNow() {
  const result = await HotCodePush.sync();
  console.log(result.status);
}

sync() runs one cycle, check, download and apply, and resolves a typed result. With the defaults the SDK runs the same cycle on its own at every start.

ReferenceCopy Anchor Link

• Installation has the AI prompt, init and the setup by hand, with the config plugin and the prebuild.
• Configuration lists every hotcodepush.json option with its type and default.
• API documents every method, event and type, useUpdates() and the statuses a result carries.
• Source on GitHub is the SDK's repository, MIT, where an issue goes.

On the deviceCopy Anchor Link

The native host asks the SDK for its bundle at every start and reload, and the SDK answers the release it serves. Applying an update reloads the JavaScript inside the running process: in-memory state is gone, which setRestartAllowed() and applyStrategy: manual are for. A release that does not come up is rolled back at the next start (Readiness).

A debug build, the development build among them, takes no updates. expo-updates and the SDK cannot share one binary, so the prebuild refuses the pair. How an update reaches a device is the lifecycle.