Android developer verification has been in the news for a year, mostly as "sideloading is changing". That part is real, but it hides the part that affects every developer on Google Play:
Apps not registered by Sep 30, 2026 will be removed from Play.
That is Google's wording, not mine. Not "cannot be updated". Removed. Globally.
The good news is that for most of you it is already done. Google says about 99% of Play apps were registered automatically. This post is for the other 1%, and for everyone who has not checked yet, because checking takes two minutes and finding out on October 1 does not.
What is actually changing
There are two separate things, and people mix them up.
1. Identity verification. Every developer who distributes apps to certified Android devices has to be a verified developer. If you publish on Google Play, you most likely already did this when Play introduced its own developer verification. Google's guide says that for most Play developers no new action is required. You can confirm it under Settings → Developer account in Play Console.
2. Package name registration. Every package name has to be registered to a verified developer, and you may need to prove you own the private signing key for it. This is the part with the September 30 deadline on Play.
Separately, from September 30, 2026 installs of apps from unverified developers are blocked on certified devices in Brazil, Indonesia, Singapore and Thailand. It expands globally in 2027. If you only publish on Play and your packages are registered, you are fine there too.
Check your status
- Open Play Console.
- Look at the Home page. Apps that still need registration are flagged there.
- Open Android developer verification to see the status of each app.
If every app shows as registered, you are done. Close the tab.
Why some apps were not registered automatically
Google registered packages based on which signing key the installs came from:
- If one key accounts for more than 50% of known installs, that key has priority.
- If no key passes 50%, every key with 50 or more installs is eligible.
- If no key has 50 installs, it is first come, first served.
So the apps that fall through are usually edge cases: an app signed with more than one key over its lifetime, an app that was also distributed outside Play with a different key, a small app with very few installs, or a package name that someone else registered first.
If you have to prove key ownership
Play Console walks you through it, but it looks scarier than it is:
- In the app list, select Add key.
- Choose the app's public certificate.
- Play Console gives you a small snippet. Put it in the APK's assets folder.
- Sign that APK with your private key and upload it.
The APK is only a proof of ownership, it does not replace your app. Your private key never leaves your machine; you only upload something signed with it. If anyone offers to "handle it" and asks for your keystore file, say no.
If you also ship builds outside Play (a direct download, another store, an internal build with a different key), register those extra keys under Android developer verification → Package names once the package itself is registered.
If you distribute outside Google Play
You need the Android Developer Console instead:
- A $25 fee and a government ID.
- Organizations need a D-U-N-S number. It is free, but Google warns it can take up to 28 days. If you are an organization and have not started, you are already late for the four launch countries.
- A limited distribution account is free, needs no ID and covers up to 20 devices. It is meant for students, hobbyists and closed groups, not for a real release.
ADB installs for your own testing keep working either way.
The checklist
- [ ] Play Console → Settings → Developer account: identity verified
- [ ] Play Console → Home / Android developer verification: every package registered
- [ ] Apps with old or multiple keys: key ownership proven with the signed APK
- [ ] Builds shipped outside Play: extra keys registered
- [ ] Organization distributing outside Play: D-U-N-S requested
If all five are ticked, September 30 is a normal Wednesday for you.
I fix Google Play problems for small teams and solo developers: target API updates, rejected releases, and now this. If one of your apps is flagged and you would rather not spend an evening on it, I do it as a fixed-price job: https://www.fiverr.com/s/61Ymq0R.
Official sources:
Top comments (0)