If you created a personal Google Play developer account after November 13, 2023, you cannot publish your app until you run a closed test with at least 12 testers opted in for 14 continuous days. This guide covers the Play Console setup, the mistakes that quietly reset your 14-day clock, and the real ways to find testers.
What Google actually requires
You need at least 12 testers opted in to your closed test, continuously for the last 14 days, before you can apply for production access. Twelve invites sent is not twelve testers. It means twelve unique Google accounts that opted in through your link and installed the app on a real device. Emulators, bots, and duplicate accounts do not count.
Organization accounts are exempt. Google dropped the minimum from 20 testers to 12 on December 11, 2024, but kept the 14-day window.
Setting up closed testing in Play Console, step by step
- In Play Console, open your app and go to Test and release, then Testing, then Closed testing. Create a new closed test track.
- Upload a build to the track. Any installable version is enough to start.
- Add testers under the track's Testers tab: paste Gmail addresses or link a Google Group.
- Send testers the opt-in link Play Console generates. Each person must open it signed into their Google account, tap Join, then install from the Play Store.
- The 14-day clock starts once the track is live and at least 12 testers have opted in. It counts from the moment you cross 12.
- After 14 unbroken days at 12 or more testers, an Apply for production button appears on your dashboard.
- Google reviews the application, usually within 7 days.
The part that catches most developers: the clock resets
The 14 days must be consecutive. If a tester opts out on day 9, their days are gone; opting back in restarts them from zero. If you drop below 12 testers total, your whole window breaks. This is why recruiting friends fails so often: people uninstall, switch phones, or forget, and one dropout on day 13 pushes your launch back two weeks.
The real goal is not 12 testers. It is 12 testers who will not leave.
Ways to find your 12 testers
- Friends and family. Free, unreliable. Works only if you can personally nag 15+ people daily.
- Swap groups on Telegram/Discord/forums. Free, slow, and feedback quality is near zero because everyone is farming opt-ins.
- Fiverr gigs. $5 to $50 for testers who opt in and vanish. Some use account patterns that look like testing farms to Google.
- A paid testing service. This is what I built TestFi for: real testers who install your app, stay opted in the full 14 days, get auto-replaced if they drop, and send written or screen-recorded feedback while they test. You satisfy Google's requirement and find out why people bounce on your onboarding in the same two weeks.
Full disclosure: TestFi is my product. The prices are public ($39.99 flat for the 12-tester bundle) and you can verify everything without talking to anyone.
FAQ
When does the 14-day clock start? Once your track is live with a build and 12+ testers have opted in. Not when you create the track.
Do testers need to open the app every day? The written rule is staying opted in for 14 continuous days. But Google's review also asks about engagement, and apps whose testers never opened them get rejected for insufficient testing.
What happens if a tester opts out? Their continuous-day count dies. Below 12 total, your window breaks and restarts.
How long does the production review take? Usually within 7 days. Budget about three weeks end to end.
Originally published on the TestFi blog.
Top comments (0)