OpenV2Docs
RomânăFAQStart Building

Publish to Google Play

The Google Play flow for Android: store listing, connecting your Google Play account, the signed bundle, the track and what happens after you submit.

Publish an Android app from the Publish button (choose Google Play) or from More → Google Play. The flow has three steps: App Info, Google Play and Submit. The release history of your project shows the real release jobs, separate from APK files you download for testing.

What you need

  • A Pro or Max plan and a successful build of your Android app.
  • A Google Play developer account, with the app created in Play Console.
  • In the app's module: a literal application ID, a version name and a version code. Phone apps must target a recent Android API level required by Google Play policy; OpenV2 checks this before you submit.

1. App Info: your store listing

Enter the title, short and full descriptions, language, a public support email and your privacy policy URL. Upload an icon, a feature graphic and 2 to 8 screenshots, or keep the images already in that language's listing. OpenV2 fits images to the sizes Google Play asks for.

2. Google Play: connect your account

Connect the Google account that manages the app, or use a service account that you invited in Play Console under Users and permissions with access to this app. OpenV2 never asks for your Google password. Connecting an account does not prove it can publish this app, so OpenV2 checks the permissions again.

For an existing app, import its registered upload key (or reuse the encrypted key saved for this project). Never create a new key for an app that already exists.

3. Submit: choose a track

Pick the release track. Internal testing is the default. Production needs an explicit acknowledgement. Finish the declarations Google requires in Play Console, then submit. You can watch the release status when you return to OpenV2.

Your first app

Google Play's API updates existing apps; it cannot create the first one. For a new app use Prepare the first signed bundle:

  1. Create a new upload key (only for a genuinely new app) or import the existing one.
  2. Build and download the signed release bundle, and the upload-key backup. Keep the backup in a private password manager: it contains the private key.
  3. In Play Console, create the app, turn on Play App Signing, upload that first bundle and complete the listing, data safety, content rating and other declarations.
  4. Connect your account in OpenV2 and submit later releases from the wizard.

New personal developer accounts may need a closed test (for example 12 testers for 14 days) before production access. OpenV2 does not bypass Google's requirements.

What "Submitted" means

Submitted means Google Play's API accepted the release on the track you chose. It does not mean Google approved or published the app. Review and release timing stay with Google. The privacy policy also has to be set in Play Console.

Privacy of your keys

Your Google credentials and upload key stay on OpenV2's servers, encrypted. Only the upload key is given to the build machine, and your source files and prompts never receive it. Private listing images are removed after submission.