After the 14 days: how to get production access on Google Play
Last updated: 1 October 2026
You finished the closed test with at least 12 testers opted in for 14 days in a row. One last step before publishing: the production access application. Here is where to apply, what Google asks, how to answer and what to do if the reply says more testing is required.
When you can apply
As soon as the closed test has had at least 12 testers opted in for 14 consecutive days, you can apply for production access from the Play Console Dashboard. Until the application is approved, the Production page stays locked.
Don’t close the test or remove testers while you wait for the answer: if Google asks for more testing, starting from a test that is still running is much easier.
Google’s questions, section by section
The form has three sections. The first is about the closed test: how easy it was to recruit testers, whether they used all of the app’s features, whether their usage matched what you expect from real users (and if not, how it differed), and a summary of the feedback you received and how you collected it.
The second is about the app: who it is for, as precisely as possible, what value it offers and how many installs you expect in the first year. These answers are only for Google and don’t appear on the Play Store listing.
The third is about production readiness: what you changed after the test and how you decided the app is ready to publish.
Answers are only saved when you move on to the next section: if you leave the page before that, they are lost. It’s worth writing them in a separate document first and then pasting them.
How to answer well
Be specific: numbers, examples and dates are worth more than generic sentences. How many testers you had, which features they tried, how much feedback you received and which problems you fixed.
Describe the changes: if you published updates during the test, say what they fixed. It is the clearest proof that the test was useful.
Tell it as it really went, including where you found your testers: Google accepts recruiting them among friends, colleagues or external services. If you found them through a swap between developers, you can say so.
Before you submit: check the app
Google points out that it is your responsibility to make sure the app complies with its policies when you apply. Before you submit the application, check these points:
- The app’s content, features and monetisation comply with the Developer Program Policies.
- The target age group and content rating really match the app.
- The app is stable: no crashes, broken features or missing screens.
- If the app requires signing in, Play Console has a working test account, so reviewers can try everything.
How long the review takes
The review usually takes 7 days or less, sometimes longer. The outcome is emailed to the owner of the developer account.
If Google replies that more testing is required
If the application doesn’t pass, Google asks you to keep running the closed test. The reasons it gives are two: fewer than 12 opted-in testers, or insufficient tester engagement during the testing period.
According to the experts of Google’s community, the “More testing required” email usually arrives when some testers didn’t have the app installed, didn’t use it consistently or left the test during the 14 days.
- Keep the closed test running and check who is still opted in.
- Replace whoever left and ask everyone to really use the app, not just install it.
- Publish an update with the fixes that came from the feedback you received.
- When the Dashboard lets you, apply again with more detailed answers.
After approval
Approval unlocks the Production page, to distribute the app to all Google Play users, and open testing.
From the Production page create a new release, upload the final build and submit it: it also goes through Google’s review before it appears on the Play Store. If you prefer, you can roll it out to part of your users at a time.
Google recommends you keep testing the app before publishing updates: the closed test can stay active afterwards too.
How TestersSeeker helps
In TestersSeeker groups the testers are developers going through the same process: they know they must stay opted in and use the app, because they need the same thing.
In the group chat you can ask what they tried, and at the end of the test everyone leaves feedback on your app with a rating and a comment: that is the material for answering the first section of the form.
If Google asks for more testing, you can open a new “I need testers” group to find people to replace the testers who left.