Google Play closed testing.
The 12-tester, 14-day rule.
For a lot of new Android developers, google play closed testing is the wall between a finished app and the public store. New personal accounts have to run a closed test with at least 12 testers for 14 days before applying for production. This is the rule, who it hits, and how to pass it.
The short answer
If your Google Play developer account is a personal account created after November 13, 2023, you must run google play closed testing with at least 12 testers opted in and actively testing for 14 consecutive days before you can apply for production access. Organization accounts and personal accounts created on or before that date are exempt. Google cut the count from 20 testers to 12 on December 11, 2024.
The rule, at a glance.
Opted in and actively testing, the current Google Play minimum
Consecutive days of testing before you can apply for production
Personal accounts created after this date have to run the test
Google cut the tester count from 20 to 12 on Dec 11, 2024
Does this apply to you
Who the rule actually hits.
The google play closed testing requirement is not for everyone. It targets one group: personal developer accounts created after November 13, 2023. If you opened a personal Play Console account recently to ship your first app, you are in scope and you will need 12 testers and 14 days before production.
Two groups are exempt. Organization accounts, the company kind registered with a D-U-N-S number, skip the closed test entirely. Personal accounts created on or before November 13, 2023 are also exempt, since they predate the policy. So the developers who hit this wall are mostly solo builders and indie founders who signed up after that date with a personal account. You can confirm your account type in the Play Console under account details.
Not sure which you have? Personal accounts are registered to you as an individual. Organization accounts are registered to a legal company and need a D-U-N-S number. The closed-testing rule follows the account type, not the app.
The requirement, exactly
12 testers, 14 consecutive days.
Here is the requirement with no rounding. To apply for production access, your app needs at least 12 testers opted in and actively testing through google play closed testing for 14 consecutive days. Both halves matter: the count and the continuity. Twelve testers for a weekend does not clear it, and neither does two testers for a month.
The continuity nuance is where most people stumble. At the time you apply, at least 12 testers have to have been opted in for the full final 14 days, continuously. Testers who opt in, poke at the app briefly, then opt out are not counted. Google is looking at how many testers stayed across the whole window, not how many ever tapped the link. That is why a tester who drops out on day ten can quietly leave you short.
The number itself used to be higher. New personal accounts once needed 20 testers, but Google reduced the requirement to 12 on December 11, 2024. The 14-day window did not change. If a guide you are reading still says 20 testers, it is out of date. You can confirm the current rule on Google’s official help page before you start.
Plan around 12 testers who stay the full 14 days, not 12 who show up once. The next section covers how to set the test up, and the one after covers how to find people who will actually last.
How to set it up
Setting up the closed test.
The setup itself is short. The work is in the 14 days that follow. Here is the path through the Play Console, from the track to the moment the test starts running.
- 1
Open the Closed testing track
In the Play Console, go to Testing, then Closed testing. You can use the default closed track or create a new one. This track is private: only the testers you add can install the build, and the app never appears on the public store while the test runs. Everything about the closed test lives in this one section of the console.
- 2
Upload your signed app bundle
Create a release on the closed track and upload your signed Android App Bundle, the .aab file. This is the exact artifact Google needs, and it has to be signed with your upload key. If you built the app with Newly, the signed bundle is what Newly produces for you, so this step is an upload rather than a build.
- 3
Add and invite your testers
Add testers by creating an email list and pasting in the addresses of the people who agreed to help, then share the opt-in link the console generates. Each tester opens the link, accepts the invitation, and installs your app from the Play Store the normal way. Aim to get more than 12 people through this step, since some will drift away.
- 4
Run the 14 consecutive days
Once testers are opted in, the 14-day window runs. Keep at least 12 of them opted in and opening the app across the full period. Check the console now and then to see how many testers are still active. When the 14 days close with the requirement met, the apply-for-production option unlocks and you can submit for review.
You need a signed bundle before any of this
Every step above assumes you have a signed Android App Bundle to upload. That is the artifact the track wants, and it is the one Newly produces when you deploy to Android. Without a signed build, there is nothing to put in front of testers.
Recruiting testers
How to recruit 12 real testers.
This is the hard part of google play closed testing, because the 12 have to be real people who stay opted in for two weeks. The build is the easy half. Finding and keeping testers is what actually decides whether you clear the requirement on the first try.
Start with people you know
Friends, family, and coworkers are the easiest testers to keep opted in for two weeks, because they will do you the favor and leave the app on their phone. Send them the opt-in link, ask them to install it and open it once in a while, and you have covered a good chunk of the 12 before you look anywhere else.
Post in communities that fit your app
Find a subreddit, Discord, Slack group, or forum tied to what your app does, and ask for testers in exchange for early access. People interested in the topic are more likely to actually use the app, which is exactly the kind of tester the 14-day window rewards. Be clear about the ask so nobody opts out on day three.
Swap tests with other developers
Indie developer communities run tester-swap threads where you test someone else's app and they test yours. It is a fair trade and a fast way to reach 12, since the other developers know the drill and tend to stay opted in for the full period. Search for closed-testing swap groups and join one.
Recruit a cushion above 12
Real people uninstall apps, switch phones, and lose interest mid-test. If you need 12 to last the full 14 days, line up 15 or 16 so a dropout or two does not reset your clock. The continuity rule counts testers who stay, so a buffer is the cheapest insurance against starting over.
The continuity rule counts testers who stay opted in, so a small buffer above 12 is worth more than a big launch-day spike that fades by day three.
Where Newly fits
Newly builds it, you run the test.
Newly is a paid AI mobile-app builder, from $25 a month. You describe the app in plain language and it generates a real React Native and Expo codebase you own. The Agent 25 plan includes Android deployment alongside iOS, so Newly produces the signed Android App Bundle you load into your google play closed testing track. The build that goes in front of your 12 testers is the one Newly hands you.
Here is the honest line. Newly automates the build and the submission, not the human requirement. It cannot be your 12 testers, and it cannot wait out the 14 days for you, because that is Google’s policy and it needs real people on real devices. So Newly gets you to a submittable build fast, and the closed test runs on top of it. Use the recruiting tips above to line up your testers, then keep 12 of them opted in for the full window.
Who does what
What Newly does vs. what you do.
The split is clean. Newly produces the app and the signed bundle. You run the closed test, because Google requires real testers and real time. Here they are side by side.
Newly handles the build
- A real React Native and Expo codebase that you own outright
- The signed Android App Bundle you upload to the closed track
- Android deployment, included in the Agent 25 plan alongside iOS
- App Store asset generation and simulators while you build
- A submittable build in minutes, not a weekend of setup
You run the closed test
- Recruiting at least 12 real testers on real devices
- Getting each tester to open the opt-in link and install
- Keeping 12-plus testers opted in for 14 consecutive days
- Nudging testers to open the app during the window
- Applying for production access once the test passes
No tool can clear the 12-tester, 14-day rule for you, since it is a human policy by design. The build, though, does not have to take you a weekend.
FAQ
Google play closed testing, questions answered.
Personal Google Play developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in and actively testing for 14 consecutive days before they can apply for production access. That is the rule in one sentence. The 12 testers have to be real people on real devices who opt into your test and keep the app installed, not 12 accounts you create once and forget. Google reduced this from 20 testers to 12 on December 11, 2024, so older guides that say 20 are out of date. Once the closed test has run its 14 days with enough testers, the apply-for-production button unlocks and you can ask Google to review your app for the public store.
Build the app, then run the test.
From $25 a month, Newly turns your description into a real React Native app and the signed Android bundle you load into closed testing. You bring the 12 testers and the 14 days. Newly brings everything up to the upload.