Production access refused: what to do next
Save the decision email and the message in Play Console. Build your next steps around the reason they give. Rewriting the application before investigating the test can leave the same problem in place.
Read the decision before choosing a fix
Google may require continued testing for too few opted-in testers or insufficient engagement. Meeting the duration alone does not establish approval. Google's production-access guidance.
Write down whether the message concerns production access, a release review, or a named policy issue. Keep separate notes for each. Follow any next steps in your own decision; do not assume someone else's waiting period applies to you.
For a continuity problem, use the opt-in troubleshooting guide. For a policy message, open the policy linked in that message and identify the affected screen or behavior.
Find what testers could actually do
Our suggested checks:
- Ask testers to describe the last task they completed. A bare confirmation that they opened the app tells you little.
- Try the same task from a fresh installation. Check onboarding, permissions, empty states and saved work.
- Give neglected features a clear task. Ask where the tester got stuck and what they expected.
- Record the build, device, problem, fix and retest result. Leave missing evidence marked as missing.
Restricted app areas need reviewer access instructions in Play Console's App content page. Google's app-review setup. Test those instructions yourself from a signed-out starting point.
A pre-launch report can flag stability, compatibility, performance and accessibility issues. Reports depend on device-lab capacity. Google's pre-launch report guide. Review one when available, alongside your human feedback.
Prepare the next application from evidence
Use a short record with four columns: finding, change, released build and retest result. Draft your answers from that record. Do not invent feedback, usage or fixes to make the test sound stronger.
Describe who tested, what they tried and what you still do not know. Explain how your latest check differs from the earlier attempt. Read the production access questions before drafting.
If the reason remains unclear, ask through Play Console's Help page with the exact decision text. Keep tester identities and login details out of public posts.