Google Play Production Access Questions: What to Write
Google's production access form has three sections and eight questions. Here is what each asks, what Google checks, and how to answer from your own records.
Read guideOnTesters blog
Google Play closed testing, explained properly
Every article cites Google’s own Help Center for the policy and labels any figure that comes from our own campaign data. No invented statistics, no approval guarantees.
Showing 8 of 65 guides
Production Access
8 guides in this topic.
Mistakes That Delay Google Play App Approval (2026)
Five mistakes that delay Google Play approval: tester dropouts, inactive testers, early applications, crashes and thin questionnaire answers, and what to fix.
Read guideTWA App Rejected: Google Says Your Testers Were Not Engaged
Google blames tester engagement and your app is a TWA. What Google actually documents, how to check whether the wrapper is the cause, and the two fixes.
Read guideWhy Play Console Shows Fewer Testers Than You Invited
Play Console can show 8 testers when you invited 18. What the closed testing count really measures, which testers silently stop counting, and how to fix it.
Read guidePlay Console Production Access: Eligibility vs Approval
Finishing 12 testers over 14 days unlocks the Apply button — it does not approve your app. What Google still reviews, and how the outcome is decided.
Read guideHow to Apply for Google Play Production Access
Where the button lives, what the three application sections ask, how to write answers that describe a real test, and the policy checks Google expects.
Read guideMore Testing Required on Google Play: What It Means
Google names two reasons for this outcome, and both are fixable: fewer than 12 opted-in testers, or insufficient engagement. How to tell which applies.
Read guideProduction Access Rejected After 12 Testers: Next Steps
You completed the window and it still did not go through. Four things to check in order, when to contact support, and why the fix is engagement.
Read guideBrowse by topic
Where developers actually get stuck
Recruitment, Play Console setup, the 14-day window and the production access application each have their own cluster. Start with the one that is actually blocking you.
Publishing12 guidesAccount types, developer verification, and the rules new Play Console accounts ship under.android-development4 guidesGuides on Google Play closed testing and production access.Setup8 guidesClosed testing tracks, opt-in links and the Play Console configuration that keeps the test valid.Compliance8 guidesThe 14-day window: what counts as an active day, what resets the timer, and how to protect the streak.Production Access8 guidesThe application, the questionnaire, and what to do when Google rejects the first attempt.Policy8 guidesWhat Google's Help Center actually requires, and how the 12-tester rule applies to your account.testing-guide2 guidesGuides on Google Play closed testing and production access.closed-testing1 guidesGuides on Google Play closed testing and production access.Recruitment11 guidesWhere to find testers who stay opted in for the full window, and the dropout risk behind each route.Tester Quality3 guidesWhat Google counts as a tester: physical devices, unique accounts, emulators and family members.
Closed testing
Need testers who stay opted in for the full 14 days?
OnTesters provides 12 real testers on physical Android devices, with replacements for dropouts and free retesting if Google asks for more testing. From $14.99.
We do not sell or guarantee production access