Skip to content

Publish an update ​

Run commands from the connected app project. The helper builds with your installed Metro bundler, signs locally, and uploads the package. The server independently verifies its signature and contents.

Latest public store version ​

sh
node ota.cjs publish ios --deployment Staging
sh
node ota.cjs publish android --deployment Staging

This performs a fresh store lookup. A failed lookup stops publication and asks for an explicit version.

A particular native version ​

sh
node ota.cjs publish ios --deployment Staging --target-version 1.4.3

The explicit version bypasses lookup, even when the store is unavailable. Use an exact compatible native version, including for a store-testing build.

Release options ​

sh
node ota.cjs publish android --deployment Staging --rollout 10 --description 'Improve account loading' --optional
OptionBehavior
--deploymentDefaults to Staging. Use Production only deliberately.
--target-versionExact native version; overrides automatic lookup.
--optionalMarks the release optional. Releases are required by default.
--rolloutPercentage from 1 to 100; defaults to 100.
--descriptionRelease notes shown in the dashboard.
--entry-fileDifferent Metro entry point.
--bundlePrepared bundle file or bundle directory instead of running Metro.

Send a tested update to Production ​

Prefer Promote in the dashboard to send the exact tested Staging artifact to Production. Direct publishing is also available:

sh
node ota.cjs publish ios --deployment Production

If an upload loses its connection, check release history before retrying. The upload may already have committed. Mutations are never automatically replayed.

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