Production Access Rejected After Closed Testing: What To Do Next
Updated 27 September 2026
A rejection usually means Google was not convinced the app was tested enough: testers did not engage, feedback and fixes were thin, or the answers were vague. Keep your closed test running with engaged testers, collect and act on real feedback, then reapply with specific answers about what testers did and what you changed.
Why applications are declined
- Little evidence of real use: testers opted in but rarely opened the app.
- No meaningful feedback or changes during the test.
- Short or generic questionnaire answers.
- The app itself looks unfinished, crashes, or breaks Play policies.
What to do now
- 1Read Google's email carefully; it may state what is missing or ask you to keep testing.
- 2Keep the closed test running with the same tester list and at least 12 opted-in testers.
- 3Collect structured feedback and ship at least one update that responds to it.
- 4Rewrite your answers with specifics: how many testers, what they tested, what issues they found, what you fixed.
- 5Reapply once Play Console lets you.
Our guarantee
12Tester Community supports your application until production access is granted, including prepared questionnaire answers. If your case matches our refund policy, you get your money back.
Frequently asked questions
Can I reapply after production access is rejected?
Yes. Continue testing, address the gaps Google pointed to, and apply again when Play Console allows it.
Do I need a new 14-day test after rejection?
Keep your closed test running rather than stopping it. Google may ask you to continue testing before you apply again, so do not remove your testers.