How to Set Up a Google Play Closed Testing Campaign
When I finished building my first Android app, I thought pushing my code to production was going to be as simple as hitting a release button. Then I encountered the Google Play Console testing dashboard. For personal developer accounts created on or after November 13, 2023, Google mandates that you run a closed test with at least 12 testers opted in for 14 consecutive days before you can apply…
Google now requires developers to run a closed test with at least 12 testers for 14 consecutive days before their app can move to production. This tester setup process has specific steps to follow to avoid delays or resets.
First, create and name your closed testing track in the Google Play Console. Newer personal accounts must adhere to this rule, while older accounts are exempt.
Next, upload a signed Android App Bundle (AAB) for review through your closed testing track. Provide release notes and click Save and Review release. Google will conduct an automated review that may take a few hours to two business days.
Once your build is submitted, choose Google Groups as the tester management method. This allows testers to join a community link automatically rather than manually entering email addresses. Create a dedicated Google Group and provide the group email address in the Play Console.
Obtain the official opt-in link from the Testers tab and share it with the Google Group members. Testers must click Become a Tester on this link while signed into the group Google account to download the app from the Play Store.
Finally, recruit 12 testers and ensure they keep the app installed for 14 consecutive days. Regularly dropping testers or sending them raw APKs can reset the 14-day streak and delay your production launch.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
