How long does Google Play production access review take?
Updated
The short answer comes from Google: once you apply for production access, review usually takes seven days or less, but can occasionally take longer, and the result is emailed to the account owner. That quote is from Google's app testing requirements page, and it is the only official number there is. We have not replaced it with an average of our own, because nobody outside Google has one worth trusting.
The more useful answer is the whole timeline, because the review is only one of five waits, and it is rarely the longest.
The full timeline, closed test to live app
| Stage | How long | Who controls it |
|---|---|---|
| 1. Closed-track release reviewed and published | Hours to days; the opt-in link can take several hours after publishing | Google, then you |
| 2. Recruiting twelve testers | Anywhere from a day to weeks | You |
| 3. Twelve testers opted in continuously | At least 14 days, fixed | The rule |
| 4. Production access application review | Usually seven days or less, per Google | |
| 5. First production release review | Varies; a separate review |
Two things fall out of that table. First, stage 3 cannot be shortened, so the realistic minimum from your twelfth opt-in to a public app is fourteen days plus two reviews. Second, stage 2 is where most of the calendar goes, and it is the only stage entirely in your hands. The fourteen days count from when twelve testers are opted in, not from when you created the track — the full requirement is here.
What slows a decision down
Google does not publish a list, so treat these as the things that are known to cause trouble rather than a guarantee of speed if you avoid them.
- Thin answers on the application. The form asks about your closed test, your app and your production readiness. Vague answers give the reviewer nothing to approve. How to answer each question.
- A test that does not look like real use. Twelve accounts that installed once and never opened the app again is exactly what the requirement exists to catch.
- Unfinished App content declarations. Data safety, content rating, target audience and the other declarations have to be complete before you can publish, so finish them during the test, not after approval.
- Policy problems in the app itself. A policy issue found at this stage is a rejection, not a delay, and it is the most expensive thing to discover late.
What to do while you wait
- Keep the closed test running. Do not remove testers or end the track. Keeping everyone opted in until the decision costs nothing.
- Keep shipping to the closed track. Fixes from tester feedback are evidence of real testing, and a new build does not restart anything.
- Prepare the production release. Store listing, screenshots, release notes and a signed build ready to go, so stage 5 starts the day you are approved.
- Plan for a refusal without expecting one. If the answer is no, the email says why, and the fix is usually more or better testing rather than a new app. What to check if access is denied.