Google Play has always verified developers. Android is now extending that idea beyond the Play Store, and the change reaches developers who distribute apps through other channels as well.
The short version for most Play developers: check your Play Console home page, confirm your package names are registered, and keep your signing keys safe. The longer version explains why.
What is changing
Android developer verification is a system-level check that links an app's package name to a verified developer. It is being introduced in stages, starting with users in Brazil, Indonesia, Singapore, and Thailand from 30 September 2026, with more regions expected later.
The goal is to make it harder to distribute malware under a trusted app identity. For users, an unverified app may trigger extra warnings or installation limits. For developers, the practical work is identity verification and package name registration.
If you publish on Google Play
Most of the work is already done for you.
- Identity verification: your existing Play developer verification generally satisfies the new requirement. You do not need to verify again for Android developer verification.
- Package name registration: Google says most Play apps have been registered automatically from information you already provided. New apps are registered when you create them in Play Console.
- Conflicts: if another developer already uses a package name, Play Console asks you to choose a different one. Do not try to force a name you do not own.
Start by opening your Play Console home page and looking for any verification or registration task. If there is no task, there is usually nothing to do.
If you distribute outside Google Play
You can use Play Console to register package names for apps you distribute on your own website, through another store, or by direct download. This helps those apps remain installable on certified Android devices.
You may need to prove ownership of the private signing key used for the package. That is why losing or sharing a signing key is more serious than it used to be.
Package names are now an identity claim
A package name is not just a folder name. It is the identifier Android uses to recognise your app across updates and stores.
- Keep the same package name for the life of the app.
- Do not reuse another developer's package name.
- Do not rename the package to escape a rejection or a registration conflict.
- Back up your upload key and keep it out of public repositories.
- Use Play App Signing so Google can manage the app signing key while you keep the upload key.
If you are unsure how signing fits together, read Play App Signing and upload keys.
What to check this week
- Open Play Console and check for verification or package registration tasks.
- Confirm that every live app has the package name you expect.
- Confirm that you still control the upload key for each app.
- If you distribute outside Play, decide whether those package names need registration.
- Remove package names you no longer use from old test projects if they could be confused with a real app.
What not to do
- Do not create a second developer account to get around a registration conflict.
- Do not upload an app under a package name you do not own.
- Do not share signing keys in chat or commit them to a repository.
- Do not assume a Play listing makes every distribution channel automatically verified.
- Do not panic and rename a live app; changing the package name creates a new app identity and loses update continuity.
Does this replace the closed test?
No. Android developer verification is about identity and package ownership. The 12-tester closed test is about app quality and production readiness for eligible new personal accounts. They can both apply to you.
If you are still working through the testing requirement, start with Google Play's 12-tester, 14-day rule.
The short version
- Android developer verification is rolling out region by region.
- Play developers usually already meet the identity part.
- Check Play Console for package name registration tasks.
- New Play apps are registered automatically; conflicts must be resolved, not forced.
- Keep your package name stable and your signing key private.
- Apps distributed outside Play can also be registered through Play Console.
Next: Play App Signing and upload keys or Play Console account types.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.