Day15 › Guides

“Your app requires more testing to access Google Play production”: what it means and what to do

Checked against Google’s Play Console Help on Oct 29, 2026 · By Anchor Point Apps

You applied for production access, waited for the review, and got an email saying your app needs more testing. Here is what Google’s documentation says that means, and a practical checklist to get unstuck.

A note on wording. The exact text in your email or Play Console can differ from the headline above, and developers report slightly different phrasings. This guide is built on what Google’s help article says about the situation, quoted below.

What Google says it means

Google’s testing-requirements article says that after you apply, Google reviews your submission and emails the account owner, and that review “usually takes seven days or less, but can occasionally take longer.” It then says:

“If your app requires additional testing, you may need to continue running your closed test. Reasons for required continued testing include having fewer than 12 opted-in testers or insufficient tester engagement during the testing period.”

So Google names two reasons: (1) fewer than 12 opted-in testers and (2) insufficient tester engagement. Google’s article doesn’t give an exhaustive list or a numeric engagement threshold, so don’t trust anyone who claims to know one.

Step 1: check the tester count, not just the invite list

• The rule is at least 12 testers opted in to your closed test, continuously for the 14 days before you applied. Inviting 12 email addresses isn’t the same as 12 people opting in.
• Remember the FAQ rule: a tester who opts in, tests for fewer than 14 days and opts out doesn’t count, and if someone opts out and back in, the 14 days must be consecutive to count.
• If you were at exactly 12 and even one person dropped, that’s the most likely cause. See what happens when testers opt out.

Step 2: look at engagement honestly

Part 1 of the application (“About your closed test”) asks how easy it was to recruit testers, whether testers used all available features, whether their usage matched what you expect from real users (with details on any differences), and a summary of the feedback you received and how you collected it. If your answers were thin, or the reality was “12 people installed it and never opened it,” that’s a plausible reason Google asks for more testing. (That last sentence is our reading, not a statement from Google.)

Step 3: keep the closed test running and make it real

1. Keep the test live. Google’s wording is that you “may need to continue running your closed test.” Don’t unpublish the track or remove testers.
2. Tell testers what to do. Google recommends clear instructions on how to test and report bugs, and the kind of feedback you want. Ask them to try as many features as they can.
3. Open a feedback channel (email, a form, or a messaging group). Testers can also leave private feedback in Google Play, which you read under Monitor and improve › Ratings and reviews › Testing feedback.
4. Fix what they report and ship updates to the closed track. Google says responding to feedback and resolving bugs improves the odds of a successful application, and Part 3 asks what you changed based on the test.
5. Keep a log of feedback received and changes made. Google’s own tip is to maintain a record, since you must summarize testing feedback when you apply.

Step 4: add a buffer before you re-apply

Our practical advice (not a Google rule): don’t aim for exactly 12. Recruit extra testers so a couple of drop-outs don’t break the count, and check your opted-in count in Play Console before you hit Apply again. See how to find and keep 12 closed testers.

What Google doesn’t tell you

Google’s help article doesn’t state how long you must wait before re-applying, or exactly how it measures engagement. Check your Dashboard in Play Console for what it currently shows, and use Help › Contact support there if the message is unclear.