OOmnistu

Blog / Startup Guides

Startup Guides

Google Play release tracks and review statuses explained

Understand Google Play testing tracks, publishing statuses and review timing so a release plan does not assume instant approval.

OOmnistu
Reviewed 2026-11-16 · 2 min read

Our iOS guide covers Apple's review. For Android, Google Play Console shows the publishing status of your app, updates and items such as a release or store listing (https://support.google.com/googleplay/android-developer/answer/9859751). Knowing the statuses tells you what is happening and what to do next.

App status: where your app is available

Status What Google says it means
Draft No presence on Google Play: not published yet, or rejected in review
Internal testing Available to internal testers by URL only, not discoverable
Closed testing Discoverable, but only selected testers can install
Open testing Discoverable, any user can become a tester; you can limit testers
Pre-registration Users can pre-register and are notified at launch
Production Available to Google Play users in your chosen countries or regions
No active releases No updates rolled out on any track, or updates were rejected
Unpublished Removed from Play by you; discoverable only to existing users
Removed by Google Removed indefinitely; submit a policy-compliant update to reinstate
Suspended by Google Removed indefinitely; needs a successful appeal to reinstate

Update status

Google lists statuses including No pending changes, In review, Update rejected and App rejected. "App rejected" applies only to first-time publishing of an app in Draft; "Update rejected" applies to updates. In both, the page says you can fix the issue and resubmit or submit an appeal.

Timing

The page notes that for certain developer accounts, Google takes more time to review an app to protect users, which may mean review times of up to seven days or longer in exceptional cases. Plan a buffer rather than a launch date that assumes instant approval.

A staged rollout plan (our suggestion, using the tracks above)

  1. Internal testing with your own team, checking install and sign-in.
  2. Closed testing with a small group of real target users.
  3. Open testing if you want wider feedback and are ready for it.
  4. Production once critical flows pass your test plan (see our testing guide).

Limits

We read the status definitions, not the Play policy documents themselves. Policy content, such as data safety forms and permissions rules, needs its own review before submission. For iOS see our App Store checklist.

By Omnistu.

Sources

Previous
Google Play Data safety form and User Data policy: what an app team has to build and declare