Appearance
Staging & Production
Staging is for approved test installations. Production is for regular users. Each platform app has both deployments, on the same server with the same signing identity.
One native build
Build with the generated Production configuration and enable test-device pairing. Distribute through TestFlight or a Google Play testing track, then promote that same build to the public store.
Pairing decides who receives Staging. Track and version do not decide access: paired and unpaired installations of 1.4.1 can safely use different channels.
Test an update
- The tester generates a code in the app's OTA testing panel.
- The owner approves it in Test devices.
- Publish to Staging:
sh
node ota.cjs publish ios --deployment StagingUse android for the Android project. Omit the version to detect the latest public store version, or add --target-version 1.4.1 for a specific build, including a newer testing-track build. Lookup failure stops and asks for a version.
Check startup, the changed feature, signatures, immediate updates and rollback.
Promote the tested artifact
Select the verified Staging release and click Promote, choose Production and confirm. Promotion copies the signed artifact without rebuilding it. Production installations must match its version and runtime and be eligible for its rollout.
Paired installations stay on Staging. Remove them in Test devices, or choose Leave testing in the app, to return to Production. See removal and offline behavior.
Monitor the rollout
Watch download, ready and failed counts alongside crash monitoring. Pause or roll back if the update behaves unexpectedly.
Older fixed-channel builds remain supported until pairing is enabled for their app. Once enabled, a Staging key alone no longer grants update access.