Appearance
Uninstall completely
Run from your mobile app root. The removal itself needs no dashboard login or OTA server connection.
Remove the project integration
sh
node ota.cjs uninstallPreview the changes first if needed:
sh
node ota.cjs uninstall --dry-runIf the helper is missing, download it and remove the integration without running setup again:
sh
(
ota_setup_dir="$(mktemp -d)" || exit
trap 'rm -f "$ota_setup_dir/ota.cjs"; rmdir "$ota_setup_dir"' 0
curl -fsS https://dashboard.pushota.com/admin/assets/ota.cjs -o "$ota_setup_dir/ota.cjs" &&
node "$ota_setup_dir/ota.cjs" uninstall
)What is removed
- The publishing helper itself and
ota.config.json. - Generated platform snippets,
ota-setup/startOtaUpdates.jsandota-setup/OtaTestingEntry.jsx. - Standard panel imports and
<OtaTestingEntry />uses, plus the native pairing flag. - The vendored SDK archive and SDK dependency.
- Copied standard native settings, bundle-loader integration and JavaScript readiness wiring.
- Obsolete Android autolinking output; installed iOS pods are reconciled through CocoaPods.
Dashboard commands download into a temporary directory and remove that download even if setup fails. The helper itself is installed through the receipt, so an existing ota.cjs is preserved too.
If a generated destination existed before the first recorded setup, its original bytes are saved in the outside-project receipt and restored on uninstall. Files created by setup are removed. Rerunning setup stops before overwriting independent edits to an owned generated file; deleted generated files can still be restored by setup.
Only the installed OTA dependency is removed from the current package manifest. Scripts, other dependencies and package settings added after setup stay in place, including after repeated setup or SDK upgrades. Lockfiles are reconciled with the project's package manager. An original whole-file snapshot is restored only when no independent changes would be lost. Empty generated directories are removed. Unrelated source edits and dependencies are preserved. Package tools and CocoaPods must be available; dependency reconciliation may need network access.
Deleted configuration and older setups
Installation receipts live outside the project, so deleting ota.config.json does not prevent removal. Older installations without receipts are recognized by their exact referenced SDK archive and standard guide integration. Other untracked archives and generated-folder files are preserved: a similar filename is not proof that OTA created them. Restore the original outside-project receipt to enable complete ownership-based removal if that receipt was lost.
Receipts from older helpers cannot recover pre-installation contents they never recorded. Existing ownership and recovery records remain usable; refreshing the helper does not invent a missing original.
Current bytes of removed or restored files are saved in a private backup outside the project. The command prints that path.
Reversible source wiring
The setup guide marks newly added OTA-only imports, lifecycle wiring and Android Gradle integration with // BEGIN PUSHOTA and // END PUSHOTA. Keep these comments around only the added code. Uninstall removes those regions while preserving surrounding app code. The startup example keeps and runs the update helper's cleanup, including when startup resolves after teardown.
Always run node ota.cjs uninstall --dry-run after integrating manually or with an AI agent. Unknown custom references stop removal instead of deleting app logic by guesswork.
Interrupted or customized integration
Safe recovery
If custom code cannot be reversed safely, uninstall stops before project changes and identifies the file. It does not silently delete unrelated code or claim success with unknown SDK references.
Keep the BEGIN PUSHOTA / END PUSHOTA comments on the guided lifecycle and Gradle snippets. These comments identify the complete added block, including listener cleanup, for automatic removal. Do not place unrelated application code inside those comments. The older standard Gradle line, direct readiness call and adjacent cleanup-return adapter are also recognized.
If integration-like code existed before setup and has since been edited, the command stops for review instead of assuming that code belongs to this installation. Custom SDK calls and lifecycle arrangements outside the supported snippets also stop before any files change.
If a package or pod command fails later, resolve that tool's error and rerun the same uninstall command. The outside-project receipt is retained until reconciliation succeeds.
What stays outside this project
Shared private keys, server login sessions, remote releases and the OTA server are retained. Another project may use them. Recovery backups also remain outside the project.
Uninstall does not change an installed phone app or an existing store binary. Build and distribute a new native version to remove OTA from installed apps.