Skip to content

Recover configuration ​

Deleted config or helper ​

Open Commands & recovery for the correct dashboard app and copy Restore project configuration. Run it in the original project directory. It downloads the helper and regenerates public configuration using the existing private signing key.

To refresh only the publishing helper, use Refresh publishing helper in the same guide. It downloads to a temporary directory and runs restore-helper, preserving the existing receipt and refusing to overwrite an independently edited helper. It also works when ota.config.json was deleted; if the outside-project receipt is missing, restore project configuration first.

Repeat for both platforms when applicable. Recovery does not reinstall the SDK or silently replace the signing key.

Lost private key ​

Restore the original key from secure backup and pass --private-key during setup. The helper checks that it matches the registered app key.

A public key or server backup cannot reconstruct the private key. A replacement trust key requires a new native build distributed through the store.

Check the connection ​

sh
node ota.cjs doctor ios

Use android for the other platform. This checks configuration and the server connection; it does not prove native runtime compatibility.

End the workstation session ​

sh
node ota.cjs logout

To remove the integration completely, follow uninstall. It works without dashboard login, including when the config has been deleted.

Setup preserves generated-file edits ​

Setup records original contents before replacing a pre-existing generated destination. Uninstall restores those originals. If you later customize an owned generated file, another setup run stops and identifies it rather than overwriting the edit. Keep project customizations in your app source, or move the customized file before refreshing generated helpers. Deleting a generated file or ota.config.json is still recoverable using the dashboard setup command; the original receipt remains outside the project.

CI credentials now require OTA_TOKEN_SERVER alongside OTA_TOKEN in protected CI settings. A missing or mismatched origin stops before sending the credential. See CI publishing.

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