Skip to content

Troubleshooting ​

Store lookup failed ​

Verify the app ID, country and public availability. Retry, or publish with the intended --target-version. A failed lookup publishes nothing and never substitutes a saved/local version.

sh
node ota.cjs publish ios --deployment Staging --target-version 1.4.3

See store detection limits for testing tracks, regional propagation and device variants.

Upload connection failed ​

Check release history before retrying. A lost response can occur after a successful publish. Mutations are never automatically replayed.

Signing key does not match ​

Restore the existing app key from secure backup. Do not generate a replacement for an installed native trust key. See recovery.

An update rolled back ​

Check whether essential startup completed and the readiness acknowledgement ran within the foreground trial. Inspect your application's crash logs. Known-failed package hashes stay suppressed; publish corrected content instead of repeatedly offering the same broken bundle.

Uninstall could not finish package or pod cleanup ​

Retain the printed backup and rerun after resolving the tool's error. Do not delete the outside-project receipt first. If uninstall identifies custom SDK usage, review that integration before retrying.

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