Check these first
- In the questionnaire, describe concretely how you recruited testers, what feedback you got, and what you changed.
- Empty answers like "no bugs, no feedback" invite rejection. Cite real cases, even small improvements.
- Applying with visible real usage (launches, retention) is safer than applying the moment you scrape past the count.
- If rejected, classify the reason — insufficient testing evidence, app quality, or policy — and reinforce only that part before reapplying.
Read alongside the official docs
Platform policy changes, so treat this page as a reference checklist and confirm the official documentation before your final submission.
Frequently asked questions
- Q. When can I apply for production access?
- Once you meet the closed testing requirement (at least 12 testers, 14 continuous days), the production application becomes available in Play Console. Applying after you have acted on test feedback tends to pass more often than applying immediately.
- Q. What should I write in the production questionnaire?
- Describe how you recruited testers, how they actually used the app, the feedback you received and what you did with it, and who your target users are. If you recruited through an exchange platform, describe that process and the feedback cases as they happened.
- Q. If production access is rejected, do I start over?
- No. Your closed testing record is retained and you can reapply after addressing the reason. If the reason was insufficient testing evidence, build up more tester activity before reapplying.
Post whatever is blocking you
Include your app name, platform, current launch stage, and the docs you already checked — it helps answerers narrow down the cause.