Google Play Publishing

Submit an Android App to Google Play Without Skipping the Review Gates

Submitting an Android app to Google Play is a sequence of reviewable states: create the app record, complete required content, prepare a release, resolve blockers and submit the changes. Saving an AAB upload does not mean the app is live.

By Updated 2 min read

Prepare the app record

In Play Console, create or open the correct app and complete the Dashboard setup tasks. Verify package ownership, display information, contact details and distribution choices before preparing production content.

Use a stable package name. Android update continuity depends on package and signing identity, not the marketing title shown in the store.

Prepare the intended release track

The current release area is under Test and release. Choose the appropriate testing track or Production, then prepare a release with the intended artifact and release notes. New personal accounts may need the required closed-test and production-access process before production is available.

Inspect the included bundle's version code and signing information. Do not accidentally promote an old testing build because its filename looks correct.

Complete the content gates

Review listing text and graphics, privacy policy, Data Safety, audience/rating, ads, app access and any permission declarations applicable to the product. Compare these with the exact release configuration.

Before pressing submit Check
Artifact Correct variant, version and target SDK
Review Credentials and instructions work from a clean state
Listing Claims and images match shipped features
Operations Monitoring and support are ready

Resolve the displayed release errors and inspect warnings rather than assuming they are decorative.

Distinguish review from publication

Publishing controls and managed publishing can affect when approved changes become available. Read the state shown in Publishing overview and the release page. Avoid promising an exact review completion time based on a previous app.

After availability, verify the store listing and installation using the intended market and account conditions. Track failures by version so a staged release can be paused or corrected.

APKLint's policy tools assist preparation; they do not upload or submit your app. Use the official setup, release and review guides for the current workflow. Keep the submitted artifact and evidence together for later troubleshooting.

Sources and further reading

  1. Google Play: Create and set up your app
  2. Google Play: Prepare and roll out a release
  3. Google Play: Prepare your app for review

Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.

APKLint

Android inspection tools and practical release guides. About APKLint · Report a correction