Google's developer verification deadline is 30 September
From 30 September 2026, certified Android devices in four countries block installs of apps whose developers have not verified an identity — and it is not only Google Play. What to do, and by when.
· 5 min read
On 30 September 2026, certified Android devices in Brazil, Indonesia, Singapore and Thailand start blocking installs of apps whose developer has not verified an identity with Google. Not just from Google Play — from the Samsung, Xiaomi, OPPO, vivo, Honor and Transsion stores too, and from a downloaded APK.
If you ship Android and you have not looked at this, look now. It is four weeks away, and the failure mode is not a rejection email — it is installs quietly failing on other people's phones.
What Google is actually requiring
Two separate things, and people conflate them:
- ·Verify your identity. A one-time check of who you are — legal name, address, and for organisations a D-U-N-S number. Most existing Play developers did this years ago and do not repeat it.
- ·Register every package name. Each app you distribute has to be registered against your verified identity. This is the part people miss, because it is per-app, not per-account.
Google says over 99% of apps from existing Play developers are already registered. The exposure is concentrated in exactly two groups: developers who publish outside Play, and people who created an account recently and have not shipped yet.
The reach is the surprising part. This is a device-level requirement on certified Android, not a Play Store policy. An app you distribute as an APK from your own website is in scope on those devices, from that date, in those four countries. Google has said the requirement expands globally from 2027.
What to do this month
- ·Open Play Console → Account detailsand confirm verification status is complete, not “action required”.
- ·List every package name you ship — including the ones distributed outside Play, and the ones you forgot were still live — and confirm each is registered.
- ·If you distribute outside Play at all, register through the Android Developer Console, which exists for exactly that case.
- ·Organisations: start the D-U-N-S lookup early. Getting a number can take days, and it is the step that turns a fifteen-minute task into a two-week one.
Why this lands on small developers hardest
A studio has someone whose job includes reading policy email. A solo developer who shipped an app eighteen months ago and moved on has an old address in their account, an unread notification, and no idea installs are about to start failing in four countries.
The verification itself is not hard. Noticing that it applies to you is the hard part, which is the whole reason this post exists.
While you are in there
Two other Android deadlines have already passed and are worth checking in the same sitting. Since 31 August 2026, Play requires new apps and updates to target API 36 (Android 16) — a submission targeting lower is rejected at upload, with a one-time extension to 1 November available in Play Console. And the Data Safety form and content rating questionnaire have to be completed by a human in Play Console; there is no API for either, so no tool can do them for you.
NoMac checks target API and developer-verification status before it uploads anything, so these fail on your machine in seconds instead of after a Play round-trip. The forms it can only pre-fill and hand to you — see the same problem on Apple's side.
Sources worth reading yourself
Google's own pages are short and unambiguous: developer.android.com/developer-verification for the requirement, and the Play Console help centre for the account-level steps. Policy dates move; check the source before trusting any blog, this one included.