Google states that all Google Play package names must be registered by September 30, 2026 to meet Android developer verification requirements. Play apps that remain unregistered after the deadline may be removed from Google Play under the Play Console requirements policy.
What is changing?
Android developer verification introduces two important tasks for developers using Google Play Console:
- Verify the developer identity associated with the account.
- Register the Android package names distributed by the developer.
If you previously completed developer identity verification successfully, Google says you generally do not need to repeat that step. However, you should still confirm that your package names have been registered.
Will Google automatically register my Play app?
In many cases, yes. Google says it will attempt to automatically register eligible existing and new Google Play apps according to package-name eligibility rules.
That means many developers may not need to manually register every existing Play app. The important step is to check the status shown for your packages rather than assuming registration is complete.
Run the free AABReady Developer Verification Checker to review package registration, identity verification, signing, and related readiness items.
Run Free Verification CheckerWhat if my package is not automatically registered?
Some packages need additional registration steps. The process can differ depending on whether the package name is new or has already been used on Android.
New package names
For a new package name that has not previously been seen on Android, Google may ask for the public certificate from the signing key pair used for the app.
Existing package names
Existing package names can require stronger ownership verification. Google may ask you to identify an eligible signing-certificate fingerprint and prove control of a known signing key associated with the package.
If the certificate fingerprint you expect is not eligible for direct registration, Google provides a request process. Depending on the situation, the developer may need to provide a reason for using that package name and complete additional proof-of-ownership steps.
What should developers check now?
- Open the Android developer verification area in Play Console.
- Confirm that your developer identity verification is complete.
- Review the registration status of the package names you distribute.
- Identify the production signing certificate and SHA-256 fingerprint used by your app.
- If a package is not registered, follow the registration or ownership-verification steps shown in Play Console.
- Resolve unresolved package-registration issues before September 30, 2026.
What about apps distributed outside Google Play?
Android developer verification also affects apps distributed outside Google Play. Google's broader Android verification rollout begins enforcement for certified Android devices in Brazil, Indonesia, Singapore, and Thailand on September 30, 2026, with wider rollout planned later.
Google Play developers can manage applicable package registration through Play Console, including packages they distribute outside Google Play.
Need package registration help?
Get Help With Your Package Registration Issue
If your package is unregistered, your signing-key status is unclear, or Play Console is asking for ownership verification, review the issue and identify the next step.
Get Package Registration Help