Publishing overview

From a test build to the stores: the simulator, phone installs, the App Store and Google Play, and what each one needs.

OpenV2 builds native iOS and Android apps. What you get depends on whether you are testing or releasing.

Four steps, four results

Step	Purpose	Result	Plan
Simulator	Test while you build	Your app running in the browser	Every plan
Companion	Test on a real phone	A build installed over USB	Pro or Max
App Store	Release on iOS	A build uploaded to App Store Connect	Pro or Max, with an Apple Developer membership
Google Play	Release on Android	A signed bundle submitted to a Play track	Pro or Max, with a Google Play developer account

A test build is not a release: neither the simulator nor a phone install publishes your app.

Before you publish

Test the app in the simulator and, if you can, on a phone.
Check the name, identifiers, version and icon. See App metadata and icons.
Ask the agent to get the app ready: the Ready for the App Store recipe (type /) checks common review issues and prepares listing text.

Start publishing

Press Publish in the header and choose the store, or open More and choose App Store or Google Play.

Managed V2 Cloud authentication does not currently include Sign in with Apple. Apple login inside Companion only signs your test builds; it does not add Apple login to your app.

Before you publish an iOS app that offers third-party or social login for its main account, check App Review Guideline 4.8. When it applies you must offer an equivalent login option that meets Apple's privacy requirements; Sign in with Apple is one such option. Apps that use only their own account system are exempt. If you need Sign in with Apple, implement and test it, including the Apple configuration, before you submit.

Release status

Uploading a build, or a Submitted status, is not approval. Review, production access and release timing stay with Apple and Google.

Usage

Builds and the simulator use your plan's usage. See Plans and usage.