Did Google Play change app package registration requirements?

Did Google Play change app package registration requirements for distribution

Yes. Google Play has added package registration to the distribution path, tied it to Android developer verification, and set a deadline: Google says all Play packages must be registered by verified developers by September 30, 2026. The change is not about app quality or store listing copy, it is about proving identity and linking package names to the right developer account.

The part people get wrong is thinking package registration is the same thing as app submission. It is separate. Google now says Play Console account holders need to verify identity and register app package names, and package registration is blocked until verification steps are finished. That means distribution can be held up even when the APK or AAB itself is ready.

Google has also split the process by package status. For a new package name that has never been seen on Android, the registration flow asks for the public key certificate from the app signing key pair. For an existing package name, the flow requires proof of ownership of the corresponding private signing key, and if the key is not eligible, the developer must request use of the package name from Google.

The inconvenient part is that Google is trying to reduce package-name sharing. Its help pages say package eligibility depends on install history and key ownership, and in some cases a developer must submit a rationale for why they should be allowed to use a package name. The example Google gives is migration, where changing the package would disrupt app distribution.

This change sits next to, but does not replace, the personal-account testing rule. Developers with personal Google Play Console accounts created after November 13, 2023 still need a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Internal testing remains optional and does not count toward that closed-test requirement.

That is the second mistake people make: they assume any testing track satisfies release requirements. Google says it does not. Internal testing is for small trusted groups and early feedback, while closed testing is the track used to qualify for production access. If the tester count drops below the minimum during the qualifying period, the production-access clock does not stay warm for you.

For a team shipping a real app, the practical checklist is now different. First, finish identity verification. Second, register the package name. Third, make sure your signing key is eligible or be ready to request use of the name. Fourth, if you are on a personal account created after November 13, 2023, run the closed test with 12 continuously opted-in testers for 14 days before asking for production access.

If you already ship on Google Play, this is not a reason to panic, but it is a reason to check your account status before you plan a release date. The deadline Google published for package registration is September 30, 2026, and the verification flow now controls whether packages can be registered and published through Play. A release plan that ignores that step can stall even when development is done.

A useful way to think about the change is that Google is moving from "upload an app" to "prove the identity behind the app." Package names, keys, and developer identity are now linked together. That reduces confusion around ownership, but it also means old habits, like assuming the package name is just a technical label, no longer work.

If you want a place to organize testing and release work, DevConnect keeps the tester-exchange part free, but the Google Play rules still control production access and package registration. The platform does not replace Play’s verification steps, it only helps you coordinate legitimate testing on apps you own. https://devconnectplatform.com

The shortest accurate answer is this: yes, Google Play changed the requirements, and the change now includes package registration, identity verification, and a separate closed-testing gate for newer personal accounts. The old mental model, where distribution was mostly about uploading a build and filling out the store listing, is no longer complete.

FAQ

Does every app need package registration now Google says all Play packages must be registered to meet Android developer verification requirements by September 30, 2026. The registration process is already part of the Play Console path for developers who distribute on Google Play.

Does internal testing satisfy the personal-account production requirement No. Google separates internal testing from closed testing, and only closed testing counts toward the 12-tester, 14-day requirement for personal accounts created after November 13, 2023.

What happens if my package name is already used or my key is not eligible Google says the eligible-key list depends on install history and key ownership. If your key is not eligible, you can still register, but you must request use of the package name and give Google a rationale.

Can I skip these steps and publish anyway No. Google says package registration is tied to Android developer verification, and for newer personal accounts the production path stays disabled until the testing requirement is met.

Does this change how I should recruit testers Yes. Google still recommends recruiting testers from your own networks and target audience for closed tests, because the goal is useful feedback, not just a number in the console.