Android developer verification (2026): what it means for sharing test builds

Google now requires apps on certified Android devices to come from verified developers who have registered their package names and signing keys. Here's what that means for test builds you share outside Google Play.

Timeline

• 30 September 2026: enforced in Brazil, Indonesia, Singapore and Thailand.
• 2027 onwards: rolling out worldwide.

What happens to unregistered apps

They can still be installed, but only through Android's advanced flow (a one-time setting with a 24-hour wait) or with ADB. Testers on affected phones will hit this for unregistered test builds.

How to register a package

• Verify your identity in the Android Developer Console (a free limited-distribution account exists for students and hobbyists, for up to 20 devices).
• Register the package name with the SHA-256 fingerprint of the key that signs it.
• For packages already in use, prove you own the key by uploading an APK signed with it.

Tip for test builds

If your release key is already registered for Play, give test builds their own package name (applicationIdSuffix ".debug" in Gradle) and register that with your test key.

Check your builds automatically

Digidropp checks every uploaded APK against Google's registration status and shows the package name and SHA-256 fingerprint to register, so you know before testers do.

Digidropp · Guide · Docs · Alternatives