Android developer verification in Brazil: a QA checklist
The first phase covers seven app stores. Here is what I would check in your Android builds before the next release.
What changed on September 30?
Android developer verification began on September 30, 2026, in Brazil, Indonesia, Singapore and Thailand. This first phase covers installs from seven participating stores on certified devices running Android 7 or later. Google plans to expand protection globally in 2027.
The stores are Google Play, Galaxy Store, GetApps, OPPO App Market, V-Appstore, HONOR App Market and Palm Store. Direct APK installs and other stores are outside the initial phase. That leaves time to prepare, rather than a reason to ignore registration.
After more than 18 years as a developer, I tend to look at the build that actually reaches the device. A release checklist needs to account for how that build gets there.
References: Google's rollout guide
Check the package and the signing certificate together
Google says 99% of Play apps were registered automatically. I would still check the Play Console, especially for packages distributed outside Play.
A package name alone tells only part of the story. The Android Developer ID Status API can check its pairing with a certificate's SHA-256 fingerprint. A different registered certificate produces REGISTERED_WITH_ANOTHER_CERTIFICATE_FINGERPRINT. Treat that result as something to resolve before distribution.
For Play App Signing, compare the app signing certificate used on delivered builds. Your local upload key can be different.
References: Registration status API documentation
Five checks I would make before release
This is the checklist I would use for an Android app or mobile game:
- List production, QA, staging and regional package names alongside their distribution channels.
- Record the SHA-256 fingerprint from the certificate that signs each delivered APK. Include debug builds where relevant.
- Confirm registration in Play Console or Android Developer Console. Use the Status API when checking package and certificate pairs in tooling.
- Test clean installation and an update from the previous supported version, preserving app data. Record the device, Android version, channel and result.
- Review your testers' install path ahead of 2027. Registered builds remain an option; ADB continues to work without developer verification.
References: Play Console registration guide
What about unregistered builds?
Google documents an advanced flow for users who accept the risks, with a one-time 24-hour wait during setup. Limited distribution accounts also support up to 20 devices. Neither replaces planning for the audience you want to reach.
I would test updates separately from first installs. Signing compatibility already matters on Android, and registration adds another check. If a key is missing, investigate the signing setup and available recovery options before assuming the app is lost.
References: Official verification FAQ
Bring distribution into your QA scope
At Kakunyn, mobile game testing and software QA are services we offer. If this rollout affects your release, let's talk about the devices, channels and update paths your test coverage needs to include.
About the author
Rofli Sanches is a developer with more than 18 years of experience and a co-founder of Kakunyn.
Have a product question or need a second opinion?
Talk with the Kakunyn team about your software and quality needs.