Google Play currently requires new personal developer accounts to run a closed test with at least 12 opted-in testers for 14 consecutive days before they can apply for production access. Organization accounts are not subject to this rule at the time of writing. Recruit committed testers early, keep them opted in for the full period and answer the production access questionnaire with concrete details from the test.
On this page
Many first-time Android publishers discover the closed testing requirement only after their app is finished, when the Play Console refuses to let them publish to production. The rule was introduced for personal accounts to raise app quality and reduce low-effort submissions, and it adds at least two weeks to a launch. With some preparation it is a manageable step, and a useful one, because real testers find problems before reviewers and public users do. This article explains how the requirement works, who it applies to and how to get through it without restarting the clock.
Who the requirement applies to
The rule applies to personal developer accounts created after Google introduced it in late 2023. When it launched, the threshold was 20 testers; Google later reduced it to 12. Currently, such accounts must run a closed test with at least 12 testers who have been opted in for at least the last 14 days continuously before applying for production access. Organization accounts, which are verified as businesses with a D-U-N-S number, are not subject to it at the time of writing. Accounts created before the rule are also not affected.
Because the details have changed before, check the current wording in the Play Console help center before you plan. The dashboard of an affected account shows the requirement and your progress directly.
Personal or organization account: the strategic choice
If the app belongs to a company, registering an organization account is the cleanest way around the rule, and it has other benefits: the developer name on the listing is your company, ownership is clear and the account is easier to transfer between team members. The cost is the time needed to obtain or confirm a D-U-N-S number and pass business verification. For a solo builder or a side project, a personal account is fine, as long as you budget for the test. Both account types pay the same one-time USD 25 registration fee.
Running the closed test step by step
- Upload a signed Android App Bundle to the closed testing track, not only to internal testing, and complete the store listing basics so the test can be reviewed and published.
- Create a tester list with Google account email addresses, or use a Google Group that testers join.
- Share the opt-in link and ask each tester to accept it and install the app from Google Play on an Android device.
- Confirm in the Play Console that at least 12 testers are opted in, and add a few more as a buffer.
- Ask testers to use the app during the 14 days and send feedback; ship at least one update based on that feedback.
- After 14 consecutive days with enough opted-in testers, open the dashboard and apply for production access.
- Answer the questionnaire about your test, your app and its readiness, then wait for Google's decision.
Where tests fail and the clock restarts
The most common problem is testers who opt out or were never fully opted in. The requirement is about continuous participation, so a tester who leaves on day ten can push you below the threshold. Recruit people you can follow up with, such as colleagues, customers from your waitlist, friends who use Android or members of a relevant community, and recruit more than 12. Testers who only use iPhones cannot participate meaningfully.
The second problem is a test without activity. Google's production access application asks how you recruited testers, how they engaged and what you changed based on their feedback. Vague answers can lead to a rejection of the application and another testing period. Collect concrete feedback, fix issues and describe them specifically. "Testers reported that the login link opened the browser, so we added in-app handling in version 1.0.3" is the kind of detail that helps.
Some services offer paid tester pools. Read Google's policies before relying on them, since the purpose of the rule is genuine testing, and an application that shows no real engagement may not be approved.
How to use the two weeks well
Treat the testing period as a soft launch rather than a waiting room. Use it to finish the Data safety form, content rating and target audience declarations. Prepare final screenshots and the feature graphic. Check Android vitals for crashes or unresponsive screens on the testers' devices. For a WebView app built with Lovable, Base44 or Bolt, verify the back button, file uploads, notifications and the offline state on the variety of devices your testers own. Our guide to publishing a Lovable app on Google Play lists the Android-specific checks.
If you also publish on iOS, run TestFlight in parallel. Apple has no equivalent tester requirement, but its review is stricter, so the same testing period is a good time to prepare for Apple's minimum functionality expectations.
Getting support through the process
AppSubmitter gives hands-on assistance with the whole publishing process, including account setup, closed testing, the production access application, listings and privacy forms, until the app is live. If you have not packaged your app yet, We Set Up Your WebView App delivers configured iOS and Android apps within 72 hours, which gives you a build to start testing with almost immediately. Once you are through, the store listing checklist helps with the final production listing.
Frequently asked questions
Does the 12 tester rule apply to organization accounts?
Not at the time of writing. It currently applies to new personal developer accounts. Organization accounts require business verification with a D-U-N-S number instead.
Do the 14 days have to be consecutive?
Yes. Google currently requires at least 12 testers opted in for the last 14 days continuously. If testers drop out and you fall below the threshold, the count effectively starts again.
Can testers use iPhones?
No. Closed testing on Google Play requires testers to install the app through Google Play on an Android device with the Google account that was invited.
What happens after I apply for production access?
Google reviews your answers about the test and the app. If approved, you can publish to production; if not, you may need to continue testing and apply again.