ScaleBun OTA updates for React Native

An OTA update can change the JavaScript bundle and its assets for an existing native binary. It does not replace native code, change native permissions, or cover changes that require a new app-store release. Compatibility information such as platform, Hermes usage, and React Native version is recorded with the bundle.

When a bundle is promoted to a release, the rollout percentage can be set anywhere from 0 to 100 and changed while the release is live. Starting at 0 lets a team create the release, preview targeting, and verify who would match before any device downloads the update.

Eligibility is evaluated server-side from the release targeting rules and the SDK check payload. That payload can include country, segment ids, lifecycle stage, architecture, custom attributes, channel, app version, platform, and the current bundle hash. A target-preview endpoint can show the matching audience before rollout begins.

ScaleBun provides two separate controls. Setting a release to PAUSED stops further delivery while preserving the release, its targeting, and its history. The dedicated rollback endpoint reverses the release in one call so devices can fall back through the same delivery path on their next check.

OTA bundles are verified using a SHA-256 checksum before installation. If the downloaded bundle does not match the expected checksum, it is rejected. Bundle integrity is declared before upload using SHA-256 and the exact byte size, and the upload is committed only after an explicit finalize step. Releases can also be signed with your own RSA-3072 key under SB-OTA-RSA-SHA256-V1: only the public key is registered (the private key never needs to be submitted to the platform), the server verifies the signature when the release is finalized, and once your app embeds the public key, native code on the device verifies it again before the bundle is downloaded and refuses anything that does not verify. Signing keys can be revoked through their own endpoint.

Yes. ScaleBun supports test tokens with a limited lifetime that can be revoked before they expire. This lets a test device access a release without changing the rollout percentage for the rest of the audience or leaving a permanent credential behind.

Yes. OTA is connected to other ScaleBun surfaces. Campaigns can target users by bundle version, mandatory-update prompts can use the engagement surface, suppress checks can avoid messaging a device that is mid-download, and release views expose adoption, health, and revenue-at-risk information.

No. ScaleBun OTA bundle delivery is for React Native applications and the upload flow accepts iOS or Android bundles. Web applications continue to ship through their normal deployment process, while feature flags and staged rollouts provide a different form of release control in the browser.