If you opened a personal Google Play developer account after November 13, 2023, you can't publish to production until you've run a closed test with at least 12 testers who stay opted in for 14 days in a row. Then you apply for production access and Google reviews it.
I run TestFi, a small testing marketplace, and a lot of what we do now is exactly this. Since May we've run more than a hundred of these closed tests for other developers. This is what I'd tell a friend who just hit the "Your app requires more testing to access Google Play production" screen.
The rule, in plain words
At least 12 testers, opted in to a closed testing track.
14 consecutive days, counted per tester.
After that you apply for production access. The application asks about your closed test, and Google says the review usually takes 7 days or less.
It applies to personal accounts only. Organization accounts don't have it.
Does the 14-day clock reset if a tester drops out?
For that seat, yes. Google counts the 14 days per tester. If someone leaves on day 10 and you replace them on day 11, the new person starts their own 14 days, and you can't apply until 12 people have each done 14. One drop-out late in the test can push your date out by almost two weeks.
That's the whole reason to recruit more than 12. We put 16 on every run. Four spare seats sounds like a lot until you've watched someone uninstall on day 12.
Where to find 12 testers
Friends and family
Free. The hard part isn't getting 12 people to install, it's getting 12 people to keep the app for two weeks and open it more than once. It works if you have a group chat that owes you a favor.
Swap communities
Developers test each other's apps, through Reddit threads, Discord servers or apps built around swapping. Free in money, expensive in time: you test their apps too, and people tend to drift off once their own test is done.
Fiverr gigs
The cheapest paid route, often $5 to $15 to start. What the listing doesn't tell you is whether the testers are distinct real people on real phones, whether they stay for all 14 days, and whether they'll use the app enough to give you something to write in the application. Ask before you order.
Closed testing services
As of October 2026 they run from about $15 to $40 per app for 12 to 25 testers, and most offer a refund or a re-run if Google says no. Read the guarantee's conditions, and check whether the testers are real people or other developers in a swap.
How long does it take?
Getting the testers is the fast part, though not instant. In our public numbers (112 closed tests up to 1 October 2026), the median time from publishing a test to the 12th confirmed install was 63.6 hours, a little under three days. Twelve testers claim the seats within about two hours. The rest is two hand-offs per tester: the developer adds their Gmail to the Play Console list (median 8 hours), then the tester installs (median 19 hours). If you add testers the moment they sign up, you take a day off your own timeline.
Then the 14 days start, and then Google's review. So from "I need testers" to "approved", plan on roughly three to four weeks, not two.
Why Google refuses production access over "engagement"
The production access application asks how you recruited testers, how engaged they were, what feedback they gave, and what you changed because of it. A refusal over engagement usually means one of two things: testers installed the app and barely opened it, or the answers were vague.
What helps:
Give testers something specific to do every few days ("create an account", "try the export", "use it once on day 7"), not just "install it".
Collect their feedback in writing during the test, so you have real material to summarize later.
Ship at least one update during the 14 days that responds to something a tester said, and mention it in the application.
Answer with specifics: how many testers, what they used, a short quote or two, what you fixed.
If you got refused, you can run another closed test and apply again. Do the four things above the second time.
Is it allowed to pay testers?
Google's requirement sets the number of testers and the 14 days. It doesn't say where testers have to come from, and paid testing services and freelancers are common. What matters is that they're distinct real people using the app on their own phones. Fake accounts, emulators and one person running several accounts are the things to stay away from.
What I'd do
Start the closed test as soon as the build is stable, not the week you want to launch.
Recruit 15 or 16 people, not 12.
Give them a small task every few days and keep their notes.
Push one update during the test.
Write the production access answers from those notes, with numbers.
Disclosure, since you're reading this on a post by the founder of a testing service: TestFi's closed test is $39.99 for 16 real testers, each one leaves notes on day 7 and day 14, and if fewer than 12 are still there on day 14 we run it again for free. Details are at testfi.app/google-play-12-testers. The steps above work whatever you end up using.
If you're stuck on something specific, ask in the comments. I'll answer.
Top comments (0)