Build & automatePractical guide · updated for 2026
How to Pass Google Play Closed Testing for a New Account
New personal developer accounts must run a closed test with a set number of testers for a set period before production. Recruit real testers, get them to install and keep the app stable.
Have this ready
- A signed release build
- A list of tester Google accounts
- A channel to collect feedback and crash reports
Step by step
- 1Check the current tester number and duration requirement in the Play Console help for your account type.
- 2Create a closed testing track and upload the release build.
- 3Recruit real testers, using their Google accounts, and add them to the tester list or a Google Group.
- 4Send each tester the opt-in link and confirm they install from Play rather than a direct file.
- 5Ask testers to use the app for the full period and report crashes.
- 6Fix crashes promptly and upload new builds to the same track.
- 7Apply for production access once the requirement is met, describing what you tested and fixed.
Want it done with you?
I can walk you through it in a Magic Box, show you the exact clicks, or do it with you and keep the recording. You log in yourself; I never see your password.
Common questions
Do testers have to stay opted in?+
Yes for the required period. Removing them early can reset the requirement.
Does the testing requirement apply to organisations?+
Usually not to organisation accounts. Check your account type in the console.
What if production access is refused?+
You get a reason. Fix the described issue, keep testing, and apply again with evidence of what changed.