Why this matters
From 2027, Android phones will only install apps whose developer Google has verified. This applies to every install, including the test build Contribute installs on a tester's phone. It already applies from 30 September 2026 in Brazil, Indonesia, Singapore and Thailand.
If your test build is signed with an unregistered key, testers' phones will refuse to install it and your test will not run. Getting verified is a one-off task and takes a few weeks at most, so do it before your first Android test.
What you need to do
1. Get verified with Google
Choose one route:
You already have a Google Play Console account: complete the account verification there. Register on Google Play Console
You do not intend to publish on Google Play: use the free Android Developer Console instead. Register on Android Developer Console
Both ask for your organisation details and a D-U-N-S number, which is free but can take up to four weeks to arrive, so start early.
2. Register your app's package name and signing key
Once verified, add your game's package name (for example `com.studio.game`) and the SHA-256 fingerprint of the key you sign releases with. Google emails you when the status shows Registered. The "Register your package names" section of the guide you followed in step 1 shows exactly where to enter both. On Play Console this happens automatically when you upload a build signed with that key.
Don't have a release key yet? Create one once and keep it: Generate an upload key and keystore
To find the SHA-256 fingerprint of a key you already have: Get the fingerprint with keytool
3. Sign every test build with that registered key
Use your release key, not the debug key your engine or IDE uses by default.
Unity: Player Settings → Publishing Settings → Keystore Manager, select your release keystore, then build. Unity: Android Keystore Manager
Unreal: Project Settings → Platforms → Android → Distribution Signing. Unreal: Signing Android projects
Android Studio: Build → Generate Signed App Bundle / APK, choose your release keystore. Sign your app
Keep the keystore and its passwords safe. Every future build of the same package must be signed with the same key or phones will refuse to update it.
4. Sign every test build with that registered key
`keytool` comes with Java and Android Studio. In a terminal, in the folder with your APK, run:
keytool -printcert -jarfile yourgame.apk
Read the `SHA256:` line and compare it with the fingerprint shown in the console you registered with: Play Console → App integrity → App signing key certificate, or Android Developer Console → Packages.
They must match exactly. If they don't, the build was signed with a different key, usually the debug key, so rebuild with your release keystore.