Production Access Rejected? A Calm Recovery Plan
Google declined your production access application? How to read the outcome, fix weak testing evidence, run a stronger closed test and re-apply.
You ran a 14-day closed test, applied, and Google said no. It's frustrating, but it's common for first-time publishers, and it's fixable. This post is a recovery plan. For the application itself, see how to apply for production access.
First: don't panic, and don't tear anything down
- Keep your closed test running and your testers opted in. Starting from zero costs you another two weeks.
- Read Google's message carefully. It tells you the outcome and may point to what to improve.
- Don't create a new developer account to start fresh. Treat the rejection as feedback on your testing evidence.
Audit your testing evidence honestly
Google's production access questionnaire asks how you recruited testers, whether they used your app's features, how their use compares to your expected audience, and what you changed because of the test. Score yourself on each:
| Question to ask yourself | Weak | Strong |
|---|---|---|
| Did testers really use the app? | Opted in, rarely opened it | Daily check-ins with written feedback |
| Did they try the main features? | Only the first screen | Clear testing instructions covering core flows |
| Did you change anything? | Same build all 14 days | Updates that fixed reported issues |
| Were your answers specific? | "Friends tested it and liked it" | Numbers, named bugs, dated fixes |
These are our recommendations from how the questionnaire is framed, not a published Google scoring system.
Plan a stronger second test
- Recruit a buffer of 15-20 testers who will actually engage. TestersZone gives every app 20 seats, and testers check in daily with a server-timed session and feedback.
- Write testing instructions listing 2-4 core tasks, so testers cover your main features.
- Turn on an in-app verification code, so every check-in proves someone opened the app (see how verification works).
- Ship at least one update during the 14 days that fixes something testers reported, and reply to that feedback.
- Keep a log: our dashboard's feedback export (CSV) gives you dates and quotes.
Rewrite your answers with evidence
Swap vague statements for specifics. Instead of "testers liked the app," write something like "18 testers made 190 check-ins over 14 days. The top issue (widget not refreshing, reported by 4 testers) was fixed in version 1.0.3." On TestersZone, the Apply tab on your app page drafts these sections from your real data, with placeholders for you to complete honestly.
What to expect
Google says review "usually takes seven days or less, but can occasionally take longer." Nobody can guarantee approval, including us. A real test with real engagement and honest, specific answers is the most reliable path. Use the 14-day calculator to plan your new dates.
How we keep this accurate
Policy facts in this guide are checked against Google's Play Console Help pages, linked inline, on the date shown above. Google can change its requirements at any time, so always confirm in your own Play Console. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start free