Google is rolling out Android developer verification, a program that ties every Android app to a verified developer identity. TestApp.io sends Android builds straight to your testers, so this affects how your releases install.

This article covers what changes, when, and what you need to do.

Nothing changes for your TestApp.io releases right now

You may have seen the September 30, 2026 deadline in Google Play Console or in the press. That deadline covers Google Play and a specific list of participating app stores.

Google's official FAQ says so in plain terms: "The September 30, 2026 deadline only applies to the specific participating stores. If you distribute your app through other stores, or if users sideload your app directly, these new verification requirements won't apply to your app yet."

Builds installed from TestApp.io fall into that category. Your testers can keep installing your releases the way they do today.

What changes in 2027

Google plans a global rollout during 2027. On certified Android devices running Android 7 or higher, Android will then refuse to install an app unless a verified developer has registered its package name and signing key.

That covers direct installs, including the builds your testers get from TestApp.io. Register the package name, or Android blocks the install.

Two things to watch:

  • Every install counts, and so does every update. This is not a one-time hurdle at first install.
  • Each package name stands on its own. If you ship com.yourcompany.app.debug or com.yourcompany.app.staging next to your production build, each one is a separate package name that needs its own registration.

What you should do

1. Register your package names

Where you do this depends on whether you publish to Google Play:

  • You already publish on Google Play. Use Play Console for all your registrations, including apps you distribute outside of Play. Google registered most apps that use Play App Signing without asking, so check Play Console first. Your production package may already be done. Look under Android developer verification in the left sidebar.
  • You do not publish on Google Play. Use the Android Developer Console. A full distribution account costs $25 once and requires identity verification. Organizations also need a D-U-N-S number, which costs nothing but can take up to 28 days, so start it early. Check the D&B lookup first, because your company may already have one.
  • You are a student or hobbyist. A free limited distribution account covers up to 20 devices with no ID and no fee.

2. Register your test package names too

Your debug, staging, and QA variants count as separate package names. If your testers install them, register them. Registering a package name that has never appeared on Android takes one step: supply the public certificate of the signing key. Google asks for no further proof of ownership.

3. Register every signing key you use

If you sign your Play release with one key and your TestApp.io builds with another, say a debug key or a CI key, register both. One package name can carry several registered keys.

4. Keep your signing keys safe

Your registration depends on your signing key. Google says it cannot recover a lost signing key, and without that key you cannot register your package name. If your keystore sits on one machine, back it up somewhere durable.

Automating this in your CI pipeline

If you upload builds to TestApp.io from GitHub Actions, Fastlane, Bitrise, or another CI system, Google offers two APIs so you can skip the console:

  • The Android Developer ID Status API checks whether a package name is registered, and whether a signing certificate SHA-256 matches the record. It needs an API key and nothing else, so you can drop it into a build step as a warning.
  • The Android Developer Console API registers package names and manages keys from code. Google documents an offline OAuth flow for CI/CD pipelines.

What this does not touch

  • iOS builds. Google runs this program on Android alone. Your iOS distribution through TestApp.io works as before.
  • Installs over ADB. You can build, test, and install on your own device with adb install or Android Studio without registering anything. Google's FAQ calls this intentional, to support "developers' need to develop, test apps that are not intended or not yet ready to distribute to the wider consumer population."
  • Managed enterprise devices. Your organization's managed store can reach managed devices without registration, though Google still recommends that you register.
  • Developers in sanctioned countries, whom Google excludes from verification checks.

What if you cannot register a package in time

Google is adding an advanced flow that lets one person install apps from unverified developers after a one-time setup. The steps run slow by design: enable developer mode, confirm that nobody is coaching you, restart the device, wait 24 hours, then authenticate with biometrics.

One developer can live with that. A QA team of 40 cannot, so plan on registering your package names.

Why we are telling you early

Verifying an organization identity for the first time can take weeks, and the D-U-N-S step alone runs up to 28 days. Finish this during 2026 and your team will not notice the 2027 rollout.

Android distribution is a core part of what TestApp.io does, so we watch this closely. Google has revised the program several times since announcing it, and we will update this article as the details firm up.

Google's own references, if you want to read the source:

Last updated: September 18, 2026.

Need help? If you are unsure which of your package names need registering, or you want a hand reading your Play Console registration status, contact us and we will work through it with you.