Docs
Android developer verification and your test builds
Google now links Android apps to verified developers. On certified devices an app has to be registered, by package name and signing key, before it can be installed and updated. The first checks cover a few stores in four countries; the worldwide rollout in 2027 reaches APKs shared from install links too. Here is what that means for builds you share with testers, and what to do before then.
When it applies
- August 2026. Google opened the developer APIs, limited distribution accounts and the advanced flow for power users.
- September 30, 2026. Checks started on certified Android phones and tablets (Android 7 and newer) in Brazil, Indonesia, Singapore and Thailand, for installs from seven app stores: Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore and GetApps.
- 2027. Google plans to expand the checks to all apps on certified Android devices worldwide, whatever the download source. That includes an APK a tester downloads from an install link.
Get ready in four steps
1. Pick the console
If you publish on Google Play, use your Play Console account: apps signed with Play App Signing are registered for you, and there is a page to register apps you also share outside Play. If you never publish on Play, create an account in the Android Developer Console. A full distribution account costs a one time $25 and needs identity verification; organizations also need a D-U-N-S number, which can take up to 28 days to get.
2. Verify your identity
Give your legal name, address, email and phone number, and the documents Google asks for. Students and hobbyists can use a free limited distribution account instead, which needs no government ID and shares apps with a small number of devices the owners approve.
3. Register the package name with every key you sign with
Registration links a package name to signing certificates: you enter the key's SHA-256 fingerprint, add the snippet the console gives you to an APK's assets folder, sign that APK with the private key and upload it. The Android Developer Console accepts several keys for one package, so register each key your testers' builds are signed with, not only the store key.
4. Check before you share
Play Console and the Android Developer Console show each package as registered or not, and Android Studio Panda 4 and newer shows it when you build a signed APK. There are APIs to check and register from CI.
Which key signs the APK your testers install
You build a signed APK yourself
Register the package with the key you sign the APK with. If that is your Play upload key or the key from Play App Signing, Play Console covers it. Then upload the APK to AppForShare as usual.
You upload an .aab and testers get an APK
AppForShare turns the .aab into one APK. By default it is signed with your workspace's AppForShare test key (its SHA-256 is in Dashboard, Settings, Android signing). You cannot register that key yourself, because proving ownership needs an APK you sign with its private key, which stays with AppForShare. Before checks reach your testers, add your own upload keystore in the same place (Pro and Team) so these APKs are signed with a key you register, or sign the APK yourself and upload the .apk on any plan.
Debug builds
Builds signed with the debug key are meant for your own devices. ADB installs keep working without registration, but testers who download an APK do not use ADB. Share release signed builds with testers.
If a tester cannot install
Check the package registration status in your console first. A developer on the team can install with adb install app.apk, which needs no registration. A tester who understands the risk can turn on the advanced flow once (it has a one day wait). For everyone else, registering the package and the key is the fix.
Questions
- Do testers in other countries notice anything today?
- Not yet. Until the global rollout in 2027, the checks only run for installs from the seven listed stores in Brazil, Indonesia, Singapore and Thailand. Google's FAQ says apps sideloaded directly are not covered by the September 30, 2026 phase.
- What does a tester see when the app is not registered?
- Once checks apply to their install, an unregistered app cannot be installed or updated unless the tester has turned on the advanced flow or uses ADB. Google has not published the exact screen for every case, so plan to register before 2027 rather than rely on the workaround.
- How does the advanced flow work?
- It is a one time setup on the phone: turn on developer options, confirm nobody is coaching you, restart, wait one day, confirm with fingerprint, face or PIN, then allow installs from unverified developers for 7 days or for good. Each install still shows a warning with Install Anyway.
- Do I have to share what my app does? It is under NDA.
- No. Google says verification is about the developer's identity and does not collect information about the app's content or purpose.
- What about company devices?
- Apps installed through an organization's managed store on managed devices do not need verification, according to Google. The same app installed from a link on a personal phone does.
- Does AppForShare register my app for me?
- No. Registration proves that you own the package and its keys, so it happens in your Play Console or Android Developer Console account.
Sources: Google's developer verification pages, guides and FAQ, read November 2, 2026. Google may change dates and details. See also .aab uploads and the signing guide.