You've built the app. The iOS build is in review. Then Google Play Console tells you that before you can publish to production, you need to run a closed test with at least 12 testers, opted in for at least 14 days in a row.
For a solo developer, this is often the longest step of the whole launch. Not because it's technically hard, but because finding 12 real people and keeping them opted in for two weeks takes planning.
Here's a day-by-day plan that gets you through it without restarting the clock.
Who does this apply to?
The requirement applies to personal developer accounts created after November 13, 2023. Organization accounts (registered as a business, with a D-U-N-S number) don't have this requirement.
If you're starting a new account and can register as an organization, that's worth considering. Otherwise, plan for the test.
The rule, exactly
- It has to be a closed test. Internal testing doesn't count.
- At least 12 testers must be opted in.
- They must have been opted in for the last 14 days, continuously.
- After that, you apply for production access, which includes a short questionnaire about your test. Google then reviews the application.
The word that trips people up is continuously. If testers drop out and you fall below 12, you're no longer meeting the requirement for those days.
Day -7 to 0: Recruit before you need them
Start recruiting before your build is ready. This is the single biggest time saver.
- Aim for 15 to 20 people, not 12. Someone always leaves, switches phones, or never opts in.
- Everyone needs an Android phone and a Google account. iPhone friends can't help here.
- Ask people who'd actually use the app. Google's questionnaire asks about feedback and changes you made, so real engagement makes the application easier.
- Collect Gmail addresses, or set up a Google Group that testers join. A group is easier: add the group to the test once, and anyone who joins it becomes eligible.
Good places to find testers: friends and family with Android phones, your mailing list or waitlist, a community related to your app's topic, and other developers in the same situation (swap testing with them, and actually use each other's apps).
Day 0: Set up the closed test
1. Create the app and complete the setup tasks
In Play Console, create your app and work through the dashboard's setup tasks: privacy policy, app access (demo account), ads declaration, content rating, target audience, and Data Safety. Some of these must be done before testing tracks can be reviewed.
2. Upload a build to the closed testing track
With EAS, configure a submit profile that targets closed testing. In eas.json, the closed testing track is called alpha:
{
"submit": {
"closed": {
"android": {
"serviceAccountKeyPath": "./play-service-account.json",
"track": "alpha"
}
}
}
}
Then build and submit:
eas build --platform android --profile production
eas submit --platform android --profile closed
If the submission is rejected because the app has never had a build uploaded, upload the first .aab manually in Play Console, then use EAS Submit for everything after. Check the current EAS Submit docs, since first-upload support has been improving.
3. Add testers and share the opt-in link
In the closed testing track, add your email list or Google Group, then copy the opt-in link. Send it to every tester with clear instructions:
- Open this link on your Android phone, signed in with the Google account you gave me.
- Tap "Become a tester."
- Install the app from the Play Store link on that page.
- Please stay opted in for the next two weeks, and use the app a few times.
Step 4 matters. Say it explicitly.
4. Wait for the track to be reviewed
The first closed test release goes through review. The 14 days only start counting once testers can actually opt in.
Days 1 to 3: Confirm everyone is in
- Check the tester count in Play Console. It shows how many testers have opted in.
- Chase the stragglers personally. The most common problem is someone opting in with a different Google account than the one on their phone.
- Don't stop at 12. Keep inviting until you have a buffer of three or more.
Days 4 to 13: Keep them engaged
Opted in is the requirement, but engagement makes the production application stronger and the app better.
- Ship one or two updates to the closed track based on feedback. Each update is something concrete to mention in the questionnaire.
- Ask a specific question every few days: "Did the sign-up flow make sense?" gets more answers than "Any feedback?"
- Keep a simple log: who reported what, and what you changed. You'll use it on day 14.
- Re-check the tester count a couple of times. Catch drop-offs before you fall under 12.
Day 14+: Apply for production access
Once 12 or more testers have been opted in for 14 continuous days, Play Console lets you apply for production access. The questionnaire asks things like:
- How you recruited testers, and how easy it was
- How testers engaged with the app, and what feedback they gave
- What changes you made based on that feedback
- Who the app is for, and what value it provides
- Whether the app is ready for production
Answer from your log. Specific beats vague: "Five testers said the onboarding skipped explaining notifications, so we added a permission explainer screen in build 1.0.3" is much stronger than "We got good feedback and made improvements."
Then wait for the review. Use the time to finish your store listing, screenshots, and release notes.
What resets or delays the process?
| Mistake | What happens | Fix |
|---|---|---|
| Using internal testing | Doesn't count toward the requirement | Use the closed testing track |
| Recruiting exactly 12 | One dropout drops you below the minimum | Recruit 15 to 20 |
| Testers using the wrong Google account | They're not counted as opted in | Send clear instructions; confirm the count |
| Waiting to recruit until the build is ready | Adds a week or more | Recruit while building |
| Vague questionnaire answers | Weaker application | Keep a feedback log from day 1 |
| Paying for fake testers | Low engagement and risk to your account | Use real people who'll try the app |
The whole timeline at a glance
| When | What |
|---|---|
| Day -7 | Start recruiting 15 to 20 Android users |
| Day 0 | Finish setup tasks, submit to closed testing, share opt-in link |
| Days 1–3 | Confirm 12+ opted in; chase stragglers |
| Days 4–13 | Ship updates, collect feedback, keep a log |
| Day 14+ | Apply for production access |
| After review | Release to production |
Plan on roughly three weeks from first upload to production for a brand-new personal account, and start recruiting early to keep it there.
Don't want to manage testers, tracks, and the production access questions yourself? LetsDeployIt handles App Store and Google Play submission end to end, including the closed testing setup.
What's been the hardest part of the 14-day test for you? Share in the comments.
Top comments (0)