Did Google Play change Play Console requirements for app registration?

Did Google Play change Play Console requirements for registering apps before distribution stops working

Yes. Google Play changed two separate things, and people often mix them up: testing requirements for newly created personal developer accounts, and Play Console registration requirements tied to developer verification and continued distribution. The test gate affects production access. The registration gate affects whether apps stay distributed.

For newly created personal developer accounts after November 13, 2023, Google Play requires a closed test with at least 12 opted-in testers who stay opted in for 14 continuous days before the account can apply for production access. Google Play says production and some related features stay disabled until those requirements are met.

That is not the same thing as app registration. Google Play’s Play Console Requirements page now says developers must register their Play apps in Play Console to meet Android developer verification requirements and Play Console requirements, and it warns that remaining unregistered apps should be registered to avoid global removal from Google Play. The page also says this requirement takes effect on September 30, 2026.

The part people get wrong is thinking there was one single deadline or one single rule. There are at least two. One rule is about testing before production access for certain personal accounts. Another is about registering apps in Play Console so distribution can continue under the verification system. Google documents them on different help pages, with different purposes and different dates.

If you are checking whether distribution will stop working, start with the Play Console Home page and the registration status shown there. Google says developers with a Google Play Console account will see notifications about app registration status on the Home page, and it points developers to register any remaining apps they want to keep distributing. That is the operational step that matters, not the headline alone.

The inconvenient part is that internal testing does not satisfy the closed testing requirement for production access. Google says internal testing is for up to 100 testers and is separate from the closed test that newly created personal accounts need before production access. People sometimes assume any test track counts. It does not.

The other mistake is assuming a bigger tester count is always the answer. Google’s current requirement for the affected personal accounts is 12 testers, not 20, and they must remain opted in for 14 continuous days. If the tester count drops below the required level during that window, the count no longer satisfies the rule and the timing has to be met again.

Buying testers or installs is not a valid shortcut. Google Play policy says incentivized or inauthentic engagement can trigger enforcement, and buying testers to clear a requirement is exactly the kind of shortcut that creates risk instead of solving the gate. The clean path is to use real testers and real testing, or to exchange testing with people who are actually testing the app.

For a developer who already has an app in Play Console, the practical question is simple: is the app registered, and does the account fall under the newer verification and testing rules If yes, fix the registration status first, then verify whether the account is one of the newly created personal accounts that must complete the 12 tester, 14 day closed test before requesting production access.

A good check order is: open Play Console, review the Home page notices, confirm the app registration status, confirm the account type, then check whether production access is blocked by the closed testing requirement. Google’s own help pages separate those steps because they solve different problems. One gate keeps the app eligible for distribution, the other keeps the account eligible to publish.

If you also distribute outside Google Play, Google says Play Console can be used to register those apps too, so the registration requirement is wider than only Play Store listings. That is another place people get tripped up, because they assume Play Console registration matters only for apps already live on Google Play. Google’s current wording says otherwise.

The bottom line is yes, Google Play changed the requirements. The safer interpretation is not “distribution stops working tomorrow,” but “some unregistered or unverified apps will be forced through Play Console steps, and some new personal accounts must clear a closed test before production access.” Those are separate checks, and both deserve attention now, not after a release is blocked.

For people who want a place to coordinate real testing without paywalls or fake shortcuts, DevConnect’s model is reciprocal testing, not buying installs or using automation on someone else’s platform. The point is to get real testers on real apps, not to game a gate. https://devconnectplatform.com