Skip to content

Readiness & rollback ​

Acknowledge healthy startup ​

Call startOtaUpdates once after the app's essential startup checks have passed. It calls the SDK readiness acknowledgement, ending the candidate update's trial. Do not acknowledge before you know the app is healthy, or wait for optional analytics/network services.

The ten-second watchdog ​

The native watchdog allows ten seconds of foreground trial time. Background time pauses the budget. If the candidate does not become ready, it restores the previous healthy bundle. Reloading and rendering can add time beyond the watchdog deadline.

Silent immediate updates ​

The generated helper checks while the app is active, on return to the foreground and every five minutes. Downloads are verified before installation. Immediate installation reloads JavaScript; it does not reinstall the native app.

Offline or failed required updates keep the last healthy app usable and retry later. Known-failed package hashes are suppressed until corrected content is published.

Limits of rollback ​

Rollback restores bundle content. It cannot undo local database migrations, backend writes, native changes or store binaries. Keep data changes compatible with both the new bundle and its healthy fallback.

The device watchdog recovers one device. Automatic fleet-wide rollback based on monitoring thresholds is a separate capability and is not currently implemented.

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