Getting a production access rejection after completing 14-day testing is frustrating. But the rejection reason is always specific — and fixable. Here is how to diagnose and resolve every common cause.
A rejected production access application does not mean your app is permanently blocked from the Play Store. It means Google found a gap between what your application described and what your testing evidence showed. Every rejection has a fixable cause.
The Three Most Common Rejection Reasons
1. Insufficient Testing Evidence
The production access questionnaire asks detailed questions about how many testers you had, how they interacted with the app, and what you changed based on feedback. Vague answers — 'we had 12 testers and got good feedback' — are not enough. Google expects specific details: which features testers used, what issues they reported, and exactly what you changed in response.
Write each questionnaire answer with a minimum of 250 characters. Google flags answers that appear templated or incomplete.
2. App Quality or Policy Issues
If your app has policy violations — even minor ones — the production review will catch them. Common triggers: missing or incomplete privacy policy URL, content that violates Play Store guidelines, app requesting permissions that are not justified by its function, or store listing screenshots that do not match the actual app.
3. Developer Account Issues
If your developer account has a pending identity verification, an unresolved policy strike, or a previous app that was removed for violations, production access can be blocked at the account level rather than the app level. Check your Play Console notifications panel before reapplying.
The Recovery Checklist
- 1Read the rejection email completely — note every specific reason listed
- 2Check your Play Console for account-level alerts or violations
- 3Review your app against Google Play's Developer Policy Center
- 4Ensure your privacy policy URL is live, functional, and relevant to your app's data practices
- 5Prepare detailed testing notes: tester count, interaction patterns, specific feedback received, and changes made
- 6Push at least one app update with a release note describing improvements
- 7Resubmit only after addressing every point in the rejection
When 'More Testing Required' Appears
This specific message means Google believes your testing window did not meet the minimum. This can happen even if Play Console showed 14 continuous days — usually because the review team found that tester engagement signals were too low (installs with no app opens, no interaction data), or your questionnaire answers could not be corroborated by the testing data.
The fix: run a second 14-day window with a fresh tester pool. This time, ask testers to actually use the app — not just install it. Push one update mid-window. Document feedback. Then resubmit with a questionnaire that references specific tester actions.
How to Make Your Questionnaire Rejection-Proof
- State your exact tester count and how you recruited them
- Describe 2–3 specific features testers used during the window
- Mention at least one issue or bug reported by testers
- Describe the update you pushed in response to that feedback
- Explain why your app is ready for public distribution based on the testing outcome
Our testing service provides a participation log you can use directly in the production access questionnaire — specific enough to satisfy Google's review team.
Get Testable Evidence