If you have built an Android app and tried to publish it recently, you have probably met Google Play’s closed testing rule.New app developers often feel surprised by the fact that the Play Console denies the access to the Production option. The matter is clear – the company requires new individual accounts to provide proof of the usage of the app by real users. This tutorial describes the current version of the policy in 2026, its requirements and how to pass it without losing any weeks.
What Is Google’s 12 Tester Policy?
The Closed Testing Policy was introduced on November 13, 2023, to improve the general quality of Google Play Apps. At first, the requirement was 20 testers for the new individual developer account. But after several modifications, Google required at least 12 testers for 14 continuous days of use in your closed test.
The key facts are:
The requirement applies only to personal developer accounts registered after November 13, 2023.
You will need at least 12 testers enrolled in a closed testing track.
Testers will have to be enrolled continuously for 14 days.
The requirement is per app basis, hence for each new app, you need to complete a closed test until you get production access on the account.
Organizational developer accounts or those created before the cut-off date do not have to fulfill this requirement.
Who Has to Follow the Requirement?
The rule targets individuals who registered a personal developer account after the cut-off date. If your account was created earlier, or if you registered as an organization with a verified business identity such as a D-U-N-S number, you can usually skip the closed testing requirement. If your Play Console Dashboard shows a closed testing checklist item, the rule applies to you.
Step-by-Step: How to Pass the 12 Tester Requirement
1. Upload a Well-Functioning App Bundle
Upload an Android App Bundle (.aab), which has been previously checked for crashes, screen issues, and permission errors. Make sure your application complies with the required API level Google sets for all new applications and updates, since the releases not complying with the target SDK requirement might get blocked.
2. Fulfill All the Required App Setup Items
Before testing, make sure you have filled out the following required items: store listing, content rating questionnaire, target audience, data safety form, privacy policy URL, ads declaration. Otherwise, incomplete items might affect your release and result in rejection.
3. Set up a Closed Testing Track
Open Play Console, go to your application, click on Testing -> Closed testing -> New track. Then create a new release, upload your app bundle, write release notes and submit. Wait until the release gets approved and published, since the clock counts only testers, which are able to install the application.
4. Add Testers Using an Email List or Google Group
Create a tester mailing list using Gmail addresses for at least 12 people, or use a Google Group and invite everyone to join. A Google Group is better since you will not need to update the release to invite new testers. Prepare for more than 12 people, say 15 or 20, since some will withdraw.
5. Send the Opt-In URL
Get the opt-in URL from the track and distribute it among your testers. All testers should open the URL, sign in with the Google account you added, tap on “Become a tester” button and finally install the app from Google Play Store. Opt-in but no install will not be sufficient.
6. Ensure Testers Remain Opted in for 14 Continuous Days
This step poses problems to most people. Any tester leaving, uninstalling and opting-out can make your count fall below 12 and the days stop counting towards the requirement. Tell all testers in your group not to exit the program before being granted the production permission. Most developers include a buffer period of two days.
7. Keep Testers Truly Active
Google’s review process is designed to be able to detect fake tests. Tell testers to launch your app from time to time, use key functions, and provide feedback. Multiple Google accounts, varied devices, and genuine usage patterns seem very natural; on the contrary, a dozen accounts that installed but never used your app are a dead giveaway.
8. Get Production Access Permission
Once two weeks have passed, the Production access button will appear in the Dashboard. Go to it and click Apply, filling out the form about your test, your app, and launch readiness. Do be specific here, and describe how you gathered testers, gathered and applied feedback.
What to Write in the Production Access Application
The reviewers are reading the answers, therefore do not use general responses such as “Everything went well.” Explain what problems were detected by the testers, what bugs were fixed, and the new versions that have been released. Also mention the number of testers, the time they were testing, and how you intend to address their comments after releasing the software.
How to Find 12 Testers Legitimately
It is difficult to find people who will keep your app installed for two weeks. The best ways include:
Your friends, relatives, and colleagues: The best testers are those people since you can ask them to keep your app installed for at least two weeks.
Developer communities: There are Reddit communities, Discord channels, Telegram communities, and Facebook groups for Android developers that hold testers exchange when you test each other’s apps.
Social media platforms:Social media platforms are effective for recruiting testers. Post about your app, explain its purpose, and invite your followers to join the closed test and provide genuine feedback.
Your own audience: If your app is suitable for your social media followers, subscribers of newsletters, or students, you may use them.
Paid testing services: There are companies that sell testers. If you decide to use them, then do it cautiously since Google expects real engagement and can detect false ones. A paid service cannot guarantee your approval.
Whichever way you choose, do not use fake profiles, bots, and purchased installations that you are unable to verify. Your violation of Google Play’s policy concerning deception may result in rejection or even suspension of your account, which is much costlier than an additional two weeks.
Common Reasons for Rejection
Developers who completed 14 days and had 12 testers still get rejected sometimes. The most common causes are:
Testers dropped below 12 during the testing window.
Low engagement, with testers installing the app but never using it.
Shallow application answers that do not explain what was tested or improved.
Policy issues in the app itself, such as a missing privacy policy, wrongly declared permissions, or misleading store listing text.
A broken or very basic app, such as a single-screen template with no real function.
Account or identity verification problems, which can include ID checks and device verification through the Play Console mobile app.
If you are rejected, read Google’s email carefully, fix the stated issues, and keep the closed test running with active testers. In many cases you can reapply after a short wait, and a stronger application usually succeeds.
Does Internal Testing Count?
No. The internal test phase permits up to 100 testers without any review, thus making it ideal for rapid iteration; however, it does not contribute to the mandatory closed testing phase. Similarly, open testing is only possible when you gain production access. Perform internal testing and identify bugs at an early stage before proceeding to closed testing.
Is There a Legal Loophole?
An organization account is the only other legal option. In case you own a company, you can create an organization developer account, which is exempt from the personal account closed testing policy. Nonetheless, the process involves business verification, such as obtaining the D-U-N-S number.
A Realistic Timeline
Plan on about three weeks for your first launch:
Days 1 to 3: Finish the app, bundle, and store listing, then publish the closed testing release.
Days 3 to 5: Recruit testers and make sure all of them install the app.
Days 5 to 19: Run the 14-day test, collect feedback, and release improvements.
Days 19 to 21: Apply for production access and wait for Google’s review, which can take several days.
Final Thoughts
Google’s closed testing policy can feel like an obstacle, but it is manageable when you plan ahead. Build a stable app, recruit more than 12 genuine testers, keep them opted in for the full 14 days, encourage real usage, and write a thoughtful production access application. Treat the process as a chance to improve your product. Since Google can adjust the policy at any time, verify the latest numbers in Play Console Help before you begin, then launch with confidence. Good luck with your launch, and may your first release go smoothly and quickly today.
Frequently Asked Questions
1.Do all 12 testers need to be different people? Yes. Testers must be separate Google accounts, and Google’s checks are designed to detect artificial testing, so use real people.
2. What happens if a tester leaves during the 14 days? If you fall below 12 opted-in testers, you may need to add replacements and continue testing until the requirement is met again.
3. Is the number still 20 testers? No. Twenty was the original requirement in 2023. The current requirement is 12 testers for 14 days.
