Guides to Google Play closed testing

The 12-tester requirement, production access, and the edge cases that are not in the documentation. Written from actually running these tests — including the parts that went wrong.

The 12-tester requirement

What Google actually requires for closed testing, and the edge cases nobody documents.

Start here
The 12 testers for 14 days requirement, explained
Google requires 12 testers opted in for 14 continuous days before production access. What that means exactly, who it applies to, and how to satisfy it.
Closed testing vs internal testing: which one Google requires
Internal testing does not satisfy Google Play's 12-tester requirement. Here is the difference between the tracks and which one unlocks production access.
Does uploading a new build reset the 14-day testing clock?
Short answer: no. Uploading a new APK or AAB to your closed track does not restart Google Play's 14-day continuous testing requirement. Here is what does.
What happens if a tester opts out during your 14-day test
A tester leaving mid-test can reset your 14-day closed testing clock. Here is what Google actually counts, and what to do the day it happens.
How to verify a tester actually opted in, in Play Console
Asking a tester if they opted in is not verification. Here is where Play Console shows the real number, and how to reconcile it against your list.
Testers opted in but your count is short: 6 causes
Your testers say they opted in and Play Console still shows fewer than 12. The six things that actually cause this, and how to tell which one you have.
Closed testing opt-in link not working: what to check
Testers get a 404, 'item not found' or 'app not available' from your closed-test opt-in link. The causes, in the order to check them, and each fix.
Google Play changed 20 testers to 12: what it means for you
Google launched the closed-testing rule with 20 testers and cut it to 12 in December 2024. What changed, what did not, and why old answers still say 20.
How to set up a closed test in Play Console, step by step
Create the closed testing track, add testers by email list or Google Group, publish the release and share the opt-in link, in the order Play Console needs.
Can your 12 testers be in different countries?
Google sets no country rule for closed testers, but your track's countries decide who can install. Why a tester abroad sees 'not available', and the fix.
Do testers need to open your app every day during the closed test?
Being opted in is what counts toward the 12, not daily use. But Google's production application asks how testers engaged, so here is what to aim for.

Finding testers

Where the 12 testers come from: free exchanges, friends, paid services, what Google allows, and how to tell whether a tester is real.

Production access

Applying for production access after your closed test: the questions Google asks, how long review takes, and what to do after a refusal.

Launch readiness

What Google Play checks in the app itself before launch: target API level, permission declarations, the Data Safety form, and secrets left in the APK.