Most first time Android publishers don't find out about this rule until they're staring at it in the Play Console at 11pm.
If you're shipping a brand new app to Google Play and the app or your developer account was created after November 13, 2023, you have to run a closed testing track for at least 14 days with at least 12 active testers before you can request production access. No exception form, no expedited path. Just the wait.
It catches people because the rest of the publishing flow doesn't really hint at it. You upload your bundle, fill in the store listing, finish the data safety form, and then hit a wall when you try to push to production. The app sits in review, then gets bounced back with a message about needing the closed test first.
What an active tester actually means
This is where it trips people up. Google's definition is narrower than you'd expect.
- Your tester has to opt in by clicking the link you send them, then install the app from the Play Store.
- The opt in has to happen on a unique Google account.
- The tester needs to have used the app on at least one day during the 14 day window. Just installing it doesn't count.
- You need 12 of these, not 12 install events. So if 8 testers install on day 1 and 4 more come in on day 13, you're not at 12 yet, because some of those late ones haven't completed a full day.
The console will show how many testers currently count toward the 14 day requirement. If the number suddenly drops, it's usually because someone uninstalled or never finished the opt in.
Mistakes that quietly reset the timer
Some changes restart the 14 day clock. The ones I've seen most often:
- Removing and re-adding the same testers
- Switching the closed track between two different versions of your app in a way Google considers structurally different
- Adding a big batch of testers after the track is already running, then removing them
If you treat the closed track as a one time setup and resist the urge to keep tweaking the tester list halfway through, you'll usually be fine.
How to plan around it
The simplest move is to start the closed track the same week you start polishing your release build. Line up the 12 testers early. Friends, fellow devs, the indie hackers community, anyone with a real Google account who'll actually open the app once or twice over two weeks.
Set a calendar reminder for day 14 and request production review the day after. By then you've finished everything else in the Play Console, so you're really just waiting on the timer plus the regular review queue.
Why I built IOn Emit around this
The publishing flow has too many of these quiet rules. You shouldn't have to find out about the 14 day requirement by getting blocked at the finish line. IOn Emit walks through the whole submission process end to end, including the closed test setup, screenshot sizing, signing key handling, and the data safety form. Freemium, desktop app.
Link if you want to take a look: https://theionproject.com/ionemit
If you've shipped a first Android app since late 2023, what other rules surprised you?
Top comments (0)