Google Play's 12 testers, 14 days rule, explained

Who it applies to

Google's rule covers personal developer accounts created after November 13, 2023. Until an account meets it, Play Console keeps Production and Pre-registration switched off for the app.

Google describes the requirement for personal accounts; its Help article doesn't set it for organization accounts.

Older tutorials and videos sometimes say 20 testers. Google's Help page now says 12, so go by the current page.

What Google requires

"At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days."

Play Console Help

Three parts of that sentence matter.

• A closed test. The testers have to be in a closed testing track. Internal testing is a separate track, and open testing only becomes available after you have production access.
• Opted in. Adding someone's email to your tester list isn't enough. Each tester has to open your opt-in link and accept.
• Continuously, for the 14 days before you apply. Testers who leave partway through don't count.

Once you meet those criteria, you apply for production access from the Dashboard in Play Console and answer questions about your test, your app and its readiness. The production access questions are covered in their own guide.

How the 14 days are counted

The count is per tester, and it looks back from the day you apply. On that day, at least 12 people must have been opted in, without a break, for the previous 14 days.

• A tester who opts in late, including someone who replaces a tester who left, counts once they have 14 days of their own.
• Google's FAQ puts it this way: "Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers."
• Being opted in is the minimum. Google also lists "insufficient tester engagement during the testing period" as a reason it may ask you to keep testing, so your testers need to actually use the app.
• Shipping fixes during the test is expected. Google's own advice is to keep updating your app in closed testing while you resolve the issues testers report.
• If you have exactly 12 testers, one opt-out drops you to 11. Recruit a few more than you need.

Setting up the closed test

Closed testing opens once you have completed your app setup in Play Console. Then:

1. Open your app in Play Console, go to Test and release > Testing > Closed testing and click Manage track.
2. On the Testers tab, click Create email list. Name the list and add your testers' Google account addresses separated by commas, or upload a CSV file with one address per line. Click Save changes, then Create.
3. Select the list for the track. Email is selected by default; you can choose Google Groups instead, in which case testers have to join the group before they can opt in.
4. Add a feedback URL or email address. It appears on your opt-in page.
5. Copy the shareable link and click Save changes.
6. Create a release on the closed track with your app bundle and roll it out.
7. Send the link to your testers. Each one opens it signed in with the Google account on your list, opts in, and installs the app from Google Play.

Details that catch people out:

• The opt-in link only shows once the app's status is Published. Apps in Draft or Pending publication don't display one, and the first time you publish a test it can take several hours for the link to become available.
• If a release seems stuck, open Publishing overview. Changes listed under "Changes not yet sent for review" aren't reviewed until you click Send for review.
• Uploading a CSV replaces the addresses already on the list, and Play Console doesn't accept CSV files saved as UTF-8 with BOM.
• Testers need a Google Account (or a Google Workspace account) and an Android device with Google Play.
• If your app is paid, closed testers have to buy it; internal testers can install it for free.

Why the count falls short, or the application comes back

• A tester left the test. Their days stop counting. If they opt back in, they need 14 consecutive days from then.
• A tester is in your internal test. Someone opted in to your internal test isn't eligible for your closed test until they opt out of the internal test and opt in to the closed one.
• Someone on your list never opted in. A listed email isn't an opted-in tester.
• The address on your list isn't the account on the tester's phone. A closed test is only open to the accounts you listed, so the tester has to opt in with that one.
• You had exactly 12, and one left.
• Testers didn't really use the app. Google says you may have to keep running your closed test if you have fewer than 12 opted-in testers or "insufficient tester engagement during the testing period."
• The app has policy or quality problems. Google says its review "is not a troubleshooting step." Before applying, it asks you to check your app's content, features and monetization against its policies; that your target age group and content rating fit your audience; that the app is free of crashes, broken functionality and missing screens; and, if the app needs sign-in, that working test login details are in Play Console.

After the 14 days

Apply from the Dashboard. Google says review usually takes seven days or less, though it can take longer, and the result is emailed to the account owner. If you're approved, the Production page and open testing become available. Keep your testers opted in until you have the result, in case Google asks you to continue the test.

The application asks about your testers' engagement, their feedback and what you changed, so it helps to collect that as you go. Here is what it asks and how to answer.