Appearance
Automatic store version detection
Connect the listing once
Open Commands & recovery and connect the public store listing:
| Platform | Identifier |
|---|---|
| iOS | Bundle ID or numeric App Store ID |
| Android | Application package ID |
Choose the two-letter store country, such as NG or US. You can also pass --store-id and --store-country during setup. This connection is separate for each dashboard app.
You do not enter a new version after each store release. The server reads the current public listing whenever you publish without a target version. Check latest version previews the version, provider, country and check time.
Publish without specifying a version
sh
node ota.cjs publish ios --deployment StagingThe command prints the detected target before bundling. Replace ios with android for the other platform. Your local checkout's version is not used.
Override with an exact version
sh
node ota.cjs publish ios --deployment Staging --target-version 1.4.3The explicit version always wins and bypasses the store lookup. It may be the latest, an older compatible version, or the intended version of a store-testing build.
When lookup fails
If lookup fails, publishing stops
Missing listings, timeouts, changed store pages and ambiguous versions return an error asking you to supply --target-version. No saved version, local project version or wildcard is substituted. No update is published by that failed command.
Check the app ID, country and public availability, then retry or provide the intended native version explicitly.
What “latest” means
Apple uses its public software lookup service. Android reads the package-verified app-details record in Google Play's public page. Google does not guarantee that page's format, so an unrecognized format causes an error.
This is the version visible in the selected public storefront. It does not discover TestFlight or internal testing tracks, and cannot resolve every device-specific variant. Staged rollouts, regional availability and store propagation can differ. No store credentials are collected.
A native version is targeting information, not proof that the update matches that build's native modules. Verify compatibility before publishing. Two-component native versions are normalized, for example 1.4 becomes 1.4.0.