Yes, Google Play Added Package Registration Requirements

Did Google Play add new package registration requirements for developer verification

Yes. Google Play now requires developers to register app package names as part of Android developer verification. Google says developers with a Play Console account must complete identity verification and register package names, and apps not registered by the September 30, 2026 deadline will be removed from Play.

The part people get wrong is treating this as a simple form change. It is not just entering a package name once and moving on. Google has a package registration flow that sits on top of developer verification, and the flow includes eligibility rules that decide whether a package can be auto-registered or whether the developer must file a request.

For a new package name that has never been seen on Android, Google’s documentation says the developer provides the public key certificate from the app’s signing key pair. For an existing package name, the developer must prove ownership of the private signing key, and Google may require an additional request when the certificate is not listed as eligible.

Google also changed the way package names are assigned when multiple developers or signing keys are involved. The documented eligibility rules prioritize the majority key holder, then keys with 50 or more installs, then first-come registration below that threshold. That matters because one developer’s registration can block later registration attempts by others for the same package name.

The inconvenient part is that verification and package registration are now linked. Google says package registration is blocked until identity verification is complete, and the Play Console help pages describe package name registration as one of the required tasks to comply with Android developer verification requirements. If verification is still pending, registration does not finish.

Another thing people miss is that auto-registration is not the same as universal approval. Google says it will attempt to auto-register eligible apps, but developers can still need to submit a request through Play Console when the key is not eligible. In other words, the package name can exist, but access to that name is still controlled by the verification rules.

If you only need the practical answer, it is this: yes, Google Play added package registration requirements, and those requirements are now part of developer verification rather than a separate optional cleanup step. A developer who publishes on Play needs to finish identity verification, register package names, and handle any key-ownership or eligibility request that applies.

If you are managing an app already on Play, the safe next step is to open Play Console, check the Android developer verification area, and confirm whether the package is already registered or waiting on a request. If you are shipping outside Play, Google also points developers to Android Developer Console for identity verification and package registration. DevConnect tracks this kind of release work at https://devconnectplatform.com, but Google’s own verification and registration steps still happen in Google’s consoles.

The part that causes the most confusion is the difference between package registration and tester requirements. Package registration is about verifying who owns the app name and signing key. Closed testing is a separate release gate. Google Play’s current closed testing rule for personal accounts created after November 13, 2023 requires 12 opted-in testers for 14 continuous days before production access can be requested, while internal testing does not count toward that requirement.

That separation matters because teams sometimes try to solve one problem with the other. Buying testers, installs, or engagement is not an acceptable shortcut. Google’s policy pages warn that incentivized and inauthentic engagement can trigger enforcement, so the correct path is to use real testers and a real package registration process tied to your verified account.

For a clean release checklist, use this order: verify the developer identity, register the package name, confirm the signing key or submit the ownership request if needed, then continue with closed testing or production steps. That order matches the way Google describes the workflow, and it avoids the common mistake of treating package registration like an afterthought.

When a package name is already tied to another developer or another signing key, registration can stop even if the app itself is otherwise ready. Google’s rules favor existing install history and key eligibility, so the practical consequence is that ownership disputes now show up earlier in the publishing process. That is inconvenient, but it also means the problem is visible before a release is blocked at the end.

If you are checking whether this applies to your app, look for the registration status in Play Console and the verification prompts on the Android developer verification page. Google says notifications appear above the app list on the Home page, and the registration status can be viewed there once identity verification is complete.

In short, Google Play did add package registration requirements for developer verification, and the rules are real, current, and tied to account identity, signing keys, and package eligibility. The mistake to avoid is assuming verification ends with an ID check. For many developers, package registration is now the next gate.