The closed testing rules, one by one
- Who: personal developer accounts created after November 13, 2023. Google's page doesn't mention organization accounts.
- How many: at least 12 testers opted in to a closed test.
- How long: continuously for the 14 days before you apply. The 14 days must be consecutive.
- A tester who opts out and comes back starts over: earlier days don't carry over.
- Testers must still be opted in when you submit your application.
- Meeting these conditions makes you eligible to apply, not automatically approved.
The step-by-step setup (closed track, email list or Google Group, opt-in link) is in our 12 testers rule guide.
What Google asks when you apply for production
Once you meet the requirements, you apply from the Play Console dashboard ("Apply for production"). The form has three parts, and your answers matter as much as your test numbers.
About your closed test
How easy was it to recruit testers? Did they use all of your features? Did their usage match what you expect in production? What feedback did you get, and how did you collect it?
About your app
Who it's for, what value it offers, and how many installs you expect in the first year.
About your production readiness
What did you change based on the test, and how did you decide the app was ready?
Google says review usually takes 7 days or less, occasionally longer. So plan for at least three weeks between starting the test and getting production access.
Mistakes that get production access denied
Google names two reasons: fewer than 12 opted-in testers, or insufficient tester engagement during the test. Either way, it may ask you to keep running your closed test. In practice, those two reasons cover several mistakes.
1. Testers who opted in but never use the app
Accounts that join, install the app and never open it again. On paper you have 12 testers; in reality, no usage. It's the most common problem with test exchanges where everyone is testing dozens of apps at once.
2. Dropping below 12 at some point in the 14 days
One opt-out on day 10 is enough: your 14-day window restarts from the day you got back to 12. Many developers apply based on the count they had at the start, without checking who is still opted in.
3. No updates during the test
The form asks what you changed because of the test. If the build on day 14 is the one from day 1, that's a hard answer to give. Shipping one or two updates to the closed track, even small ones, shows the feedback was put to use.
4. Vague or copy-pasted answers
"Testers liked the app, no issues" says nothing. Describe specific feedback, the fixes that followed, the features tested and how you collected input (form, email, the test's feedback address). Stick to facts: don't invent feedback or numbers.
5. An app that wasn't ready
Crashes on launch, a login screen without demo credentials, empty features: Google states that submitting non-compliant apps and expecting reviewers to find the issues leads to rejections. Check the Play Console pre-launch report and fix blocking issues before you apply.
Setup mistakes that cost you days
These don't cause a rejection, but they stop the test from starting or make it start over.
- Closed test release not published: the opt-in link doesn't work.
- Testers' country not targeted under "Countries/regions" for the track: they can't install the app.
- Testers added to the list but never opted in through the link: they don't count.
- Closed track paused or deleted mid-test: avoid it until you've applied.
- App requires an account but no test credentials are provided: testers can't use anything.
What to do after a rejection
- 1
Keep the closed test running
Google says you may need to continue your closed test. Don't delete the track and don't let your testers go.
- 2
Fix the likely cause
Count the testers who are really opted in, nudge inactive ones, replace those who left, and fix what feedback pointed out.
- 3
Ship an update
A new build on the closed track, with changes you can describe precisely in your next application.
- 4
Reapply with specifics
Once at least 12 testers have again been opted in for 14 consecutive days, rewrite your answers with facts: feedback received, fixes made, features tested.
A closed test that lasts the full 14 days
PlayTesterHub runs your closed test on 12 physical Android devices managed in-house in France. Our team uses your app every day, keeps all 12 testers opted in for the 14 days and replaces any tester who drops out. When you ship an update, we install it on every phone. If Google asks for more testing after you apply for production, a free rerun is included (one per order).
Standard
€15
Everything you need to pass Google Play closed testing.
- 12 testers in France, on physical Android devices
- 14-day closed test tracked in real time (dashboard)
- Tester group email ready to add in Play Console
- Testing starts in under 8 hours once you add the group and confirm
Premium
€25
Your app reviewed every day, then a final report with our recommendations.
A full recap every 3 daysPerformance, crashes, feedback and advice, on top of the checks reviewed every day and the final report.- Everything in Standard: 12 testers, 14 days, in France
- Performance tests and other checks reviewed every day during the test
- A full recap every 3 days: performance, crashes, feedback, advice
- An end-of-test report with advice and recommendations
- Real-time progress tracking (dashboard)
Premium+
€40
Every device documented day by day, ready for your AI agents.
168 reports1 report per device per day, 12 a day for 14 days, ready for your AI agents.- Everything in Premium: checks reviewed every day and a full recap every 3 days
- One report per device every day: 12 reports a day, 168 reports over the 14 days
- Structured reports your AI agents can use directly (API and MCP)
- Screenshots with descriptions
- The final report with advice and recommendations
Rerun and refund conditions are in our refund policy. PlayTesterHub does not guarantee Google Play approval: Google alone decides.
Frequently asked questions
Do the 14 days have to be consecutive?
Yes. Google requires at least 12 testers opted in continuously for the 14 days before you apply. A tester who opts out and comes back starts their count again.
How long does the production access review take?
According to Google, usually 7 days or less, occasionally longer. Add the 14-day test and plan for at least three weeks in total.
Why did Google deny my production access?
The two reasons Google names are fewer than 12 opted-in testers and insufficient tester engagement. In practice that often means inactive testers, an opt-out mid-test, no updates, or answers that were too vague in the form.
Do I need to start a new closed test after a rejection?
Google says you may need to continue your closed test. The simplest path is to keep the same track running, fix the cause of the rejection and reapply once you meet the requirements again.
Should I publish updates during the closed test?
It's not a written requirement, but the form asks what you changed because of the test. One or two updates on the closed track are the simplest proof that you acted on feedback.
Can my testers leave after 14 days?
Wait until you've applied: testers must be opted in when you apply, and Google may ask you to keep testing. The safest choice is to keep them until you have production access. How to find 12 testers →