Did Google Play add new app registration requirements in Play Console?

Did Google Play add new app registration requirements in Play Console

Yes. Google Play added new Play Console registration and verification steps, and personal accounts created after November 13, 2023 now face testing requirements before production access.

The part people miss is that Google Play is not talking about one single change. Play Console now asks developers to register apps and complete account verification, while some personal accounts must also pass a closed testing requirement before production access. The app setup flow now points developers to testing tasks as part of release readiness.

There is a separate package registration requirement on top of the normal app submission flow. Google says developers with a Play Console account need to complete identity verification and register their Play package names, and it says all Play packages must be registered by September 30, 2026. That is a registration requirement at the platform level, not a change to your app’s UI or manifest alone.

For personal developer accounts created after November 13, 2023, the release path is stricter. Google says those accounts must meet specific testing requirements before they can access production, and the app dashboard now calls out the need to set up internal or closed testing, roll out a release to the test track, and gather private feedback. The old 20 tester rule is no longer the current rule for this path.

The current closed testing rule is 12 testers opted in for 14 continuous days before production access for eligible personal accounts. Internal testing does not satisfy that requirement, because Google says internal testing allows up to 100 testers and does not count toward the closed testing requirement. That distinction is the one teams usually get wrong when they try to hurry a release.

Buying testers or installs is not a valid shortcut. Google Play’s policy says inauthentic or incentivized engagement can be detected and can put the account at risk, so the safe path is to use real testers who actually install and test the app. An exchange model, where people test each other’s apps on their own accounts and devices, fits the rule.

The inconvenient part is that registration and testing are now separate gates. You can finish app setup and still be blocked from production if your account has not met the testing requirement, and you can also be blocked later if your package or account information is not registered correctly. Google also says developers should keep their account information current, because missing or stale details can affect app availability.

A practical example makes the difference clear. If you create a personal account after November 13, 2023, upload an app, and run only an internal test with 5 coworkers, that does not unlock production. If you instead run a closed test with 12 real testers who stay opted in for 14 continuous days, you meet the testing condition Google describes for that account type.

For teams that want a simple path, the safest setup is: verify the developer account, register the Play package name, create the test track, recruit real testers, and keep the closed test alive long enough to satisfy the full 14 days. If you need a place to coordinate testing without paying for access or using ads, DevConnect is built for that exchange model and keeps the workflow on your own app and your own accounts. https://devconnectplatform.com

If you are checking whether Google “changed registration,” the short answer is yes, but the change is broader than one checkbox. Google added package registration and verification requirements in Play Console, and it also tightened the pre-production testing path for some new personal developer accounts. The rule to remember is not “upload the app and publish,” it is “register the app, verify the account, and satisfy the testing gate that applies to your account type.”

FAQ

Does internal testing count toward the closed testing requirement? No. Google says internal testing supports up to 100 testers, but it does not count toward the closed testing requirement for production access.

Is the old 20 tester requirement still current? No. The current personal-account requirement described by Google is 12 testers opted in for 14 continuous days, not 20 testers.

Do all Play Console accounts need the same setup steps? No. Google separates identity verification, package registration, and testing rules, and the testing gate applies specifically to certain personal accounts created after November 13, 2023.

Can you bypass the requirement by paying for testers? No. That can create policy risk, and Google’s guidance points developers toward genuine testing rather than purchased engagement.

What should I check first in Play Console? Check whether your app package is registered, whether your developer identity is verified, and whether your account type has a closed testing gate before production access.

Can I launch if my app is already in Play Console but not registered? Google’s current guidance says unregistered apps risk removal and continued distribution problems, so registration should be completed before you rely on production availability.