Google's official answer is short: "Review usually takes seven days or less, but can occasionally take longer." There is no guaranteed turnaround, and nobody outside Google can promise you a date. The account owner receives an email when the review is finished.
This article explains what that statement covers, which other reviews people confuse it with, and how to use the waiting time well.
What Google says, exactly
The wording comes from Google's page on app testing requirements for new personal developer accounts: "Review usually takes seven days or less, but can occasionally take longer."
Two words carry the meaning:
- Usually means most reviews finish within seven days, not all.
- Occasionally means a longer review is possible and isn't a sign that something went wrong.
Google doesn't publish an average, a maximum or a way to speed it up. Treat any claim of a fixed number of days, from a forum, a video or a testing service, with caution.
Which review this is
New developers often mix up three separate reviews. Each has its own timing.
| Review | When it happens | What Google says about timing |
|---|---|---|
| Closed track release | When you send your closed release for review | "A few hours or up to seven days (or longer in exceptional cases)" |
| Production access application | After you click Apply for production | "Usually takes seven days or less, but can occasionally take longer" |
| First production release | After access is approved and you send a production release | New developer accounts may see reviews of "up to seven days or longer in exceptional cases" |
This article is about the middle row. Even after production access is approved, your first production release goes through its own review before it reaches users. Plan for that too.
What happens during the review
You apply from the Dashboard by clicking Apply for production and answering three groups of questions: your closed test, your app, and your production readiness. Google then reviews the application along with your app.
There are two outcomes:
- Approved. The Production page and Open testing are unlocked.
- More testing required. Google says "Reasons for required continued testing include having fewer than 12 opted-in testers or insufficient tester engagement during the testing period."
If you want to know what reviewers look at, see what Google looks at when you apply for production access.
What to do while you wait
The waiting days are useful if you treat them as part of the test.
Keep your closed test running
Don't remove testers, delete the tester list or unpublish the closed track. Google's own best practice is to "continue running closed tests while resolving user-reported issues and bugs." If the result is "more testing required", you'll want your testers still in place rather than starting from zero.
Keep testers engaged
Ask testers to keep the app installed and keep using it. Nothing in Google's documentation says engagement stops mattering the moment you apply. Our article on keeping testers engaged for 14 days has ideas that work just as well during the wait.
Fix what testers found
If testers reported bugs that you haven't fixed yet, fix them now and ship an update to the closed track. That's better use of a week than refreshing your inbox.
Prepare your launch
Get your production release ready so you can move quickly if you're approved:
- Check that the store listing describes only what the app really does.
- Decide which countries you'll launch in.
- Confirm that test login credentials in Play Console still work.
- Read the pre-launch report from your latest upload.
Watch the right inbox
The result goes to the account owner by email. If someone else on your team owns the account, make sure they know to forward it.
What not to do while you wait
- Don't submit a second application for the same app. Google doesn't describe this as a way to speed things up.
- Don't let your tester count fall. Testers who opt out in the middle of a review can leave you short if you have to keep testing.
- Don't change declarations to something less accurate to see whether it helps. Declarations have to match the app.
If it's taking longer than seven days
Remember the official wording: review "can occasionally take longer." A review past seven days is unusual but not, on its own, a problem. Check that:
- The application was actually submitted. Leaving the form without clicking Next or Apply loses your answers.
- The account owner's email isn't filtering Google messages.
- Your App content declarations show no new pending tasks.
Then keep testing and keep waiting. There's nothing in Google's documentation that suggests reapplying or contacting anyone shortens the review.
If the answer is more testing
Don't panic, and don't assume a fixed waiting period before you can try again. Google doesn't publish one. Continue the closed test, deal with the cause Google gave, and reapply when you're ready. Check the basics first: did you have at least 12 testers opted in continuously for the 14 days before you applied? What happens if a tester drops out explains how a single opt-out can change that count.
Key takeaways
- Officially: "usually takes seven days or less, but can occasionally take longer."
- No one can promise a review date, including us.
- The closed track review and your first production release review are separate.
- Keep your closed test and your testers in place until you have the result.
If you haven't applied yet, how to apply for production access walks through the form, and our production access guide has example answers. GoPlayTester's 12+ testers stay opted in through the full 14 days of testing, and Google makes the final decision on every application.
