Short answer: No. Google Play still says the production access review usually takes 7 days or less. What changed is the gate before you can apply, now 12 opted-in testers for 14 continuous days for new personal accounts.
No. Google Play says the production access review itself usually takes 7 days or less, and it may occasionally take longer. The part that changed for new personal accounts is the pre-review testing gate: you need a closed test with at least 12 opted-in testers for 14 continuous days before you can apply for production access.
That distinction is the part people get wrong. They treat the 14 day testing rule and the production access review as if they are the same timer. They are not. The 14 day period is the testing requirement. The review starts after you submit the production access request.
Google Play’s help page for new personal developer accounts says you must run a closed test with a minimum of 12 testers who have been opted in continuously for the last 14 days. Only after that can you apply for production access in Play Console. The same page says that after you submit the request, Google will review it and email the account owner when the review is complete, which usually takes 7 days or less. That is the current official wording.
The inconvenient part is that the clock can restart before you ever reach review. If you drop below 12 opted-in testers, or if the testers are not continuously opted in for the full 14 day span, you do not qualify yet. In that case you are still stuck in the testing step, not waiting on production review. Google’s help text explicitly says you may be asked to continue testing if you do not have 12 testers opted in or if testers were not engaged during the closed test.
Another thing people mix up is account type. This requirement is for newly created personal developer accounts. Google Play’s own testing guide says this is the rule for new personal accounts created after November 13, 2023. Community answers on Google’s support site repeat the same distinction, newer personal accounts need the closed test gate, while other account types do not follow that same path.
So the short answer is: no, Google Play did not say the production access review now takes longer as a standard rule. The review window is still described as usually 7 days or less. What changed was what you must finish before you can submit for that review.
If you are trying to plan a launch, this matters in practice. A new personal account can spend 14 days accumulating eligible testers, then wait for the production access review after submission. If the review comes back with a request for more testing, the delay is not because the review timer changed, it is because the testing evidence was not enough. That is why some developers feel like the process got longer, even though the published review estimate stayed the same.
A concrete example: if you start a closed test on Monday, March 2, and you reach 12 opted in testers that same day, you still cannot apply until those testers remain opted in continuously through the full 14 day period. If one tester leaves on day 10, you have to rebuild compliance from there. Only after you apply does the separate production access review begin.
The practical takeaway is simple. Do not use the 14 day closed test as a proxy for review time. Do not assume production access is slow just because your test phase is slow. And do not submit before the tester count and continuous opt in requirement are actually satisfied, because that is the fastest way to get sent back to testing.
If you are comparing Google Play with Apple’s TestFlight, the systems are different. Apple says TestFlight allows up to 10,000 external testers, but it does not have an equivalent of Google Play’s 14 day production access rule. That can make Google’s new personal account path feel stricter, even though it is the pre-review gate that is stricter, not the stated production review window.
For people using DevConnect, this is exactly the kind of launch constraint that matters. DevConnect is free to use, and it is built around real testing reciprocity, not paid gates or ad-driven noise. If you need a place to find testers without turning launch prep into a cold outreach project, that is the use case.
What changed, and what did not
What changed is the access requirement before production. For new personal accounts, Google Play now requires 12 opted-in testers for 14 continuous days before you can request production access. The old 20 tester requirement is no longer current.
What did not change, based on the current help text, is the production access review estimate. Google still says the review usually takes 7 days or less, though it may occasionally take longer.
What developers usually miss
They miss that the review is not the waiting period that matters first. The first wait is qualifying for the request, and that is where the 14 day span lives. If your tester list is unstable, the production review never starts.
They also miss that Play Console can ask for more testing even after a request is submitted. Google explicitly says examples include not having 12 testers opted in or testers not being engaged with the app during the closed test. That is why a request can bounce back into testing instead of moving straight to launch.
What to do next
If you are a new personal account owner, keep the tester list above the minimum before the full 14 day window ends. Then submit the production access request only after the requirement is met. If you are short on testers, keep recruiting before you restart the clock.
If you are comparing rollout paths, remember the shortcut that is not a shortcut: internal testing allows up to 100 testers and does not count toward the closed testing requirement. That can help you shake out bugs, but it does not replace the production access gate for new personal accounts.
Bottom line
Google Play did not change the stated length of the production access review for new personal accounts. It still says usually 7 days or less. The change people feel is the stricter closed test requirement before that review can even begin.
FAQ
Does the 14 day period mean the review takes 14 days
No. The 14 day period is the closed test requirement before you can apply. The review happens after you apply, and Google says that review usually takes 7 days or less.
What happens if I fall below 12 testers
You do not meet the current requirement yet. Google’s help page says your app may need more testing, and the continuous 14 day clock is part of the requirement.
Does internal testing count toward the requirement
No. Google says internal testing is separate and does not count toward the closed testing requirement for production access.
Is this only for personal developer accounts
Yes, this current closed testing gate applies to newly created personal developer accounts. Google’s help page and support community answers both frame it that way.
Can I skip closed testing and go straight to production
Not for this account type. Google says you must complete the closed test criteria before you can apply for production access.
Frequently asked
Does the 14 day period mean the review takes 14 days
No. The 14 day period is the closed test requirement before you can apply. The review happens after you apply, and Google says that review usually takes 7 days or less.
What happens if I fall below 12 testers
You do not meet the current requirement yet. Google’s help page says your app may need more testing, and the continuous 14 day clock is part of the requirement.
Does internal testing count toward the requirement
No. Google says internal testing is separate and does not count toward the closed testing requirement for production access.
Is this only for personal developer accounts
Yes, this current closed testing gate applies to newly created personal developer accounts. Google’s help page and support community answers both frame it that way.
Can I skip closed testing and go straight to production
Not for this account type. Google says you must complete the closed test criteria before you can apply for production access.
Sources
- App testing requirements for new personal developer accounts - Play Console Help
- Google Play Developer Community: closed testing
- Google Play Developer Community: organization and personal accounts
- TestFlight - Apple Developer
- TestFlight overview - App Store Connect Help
Originally published at devconnectplatform.com, where it is kept up to date.
