Package name auto-registration process in Play Console

Overview

Google Play Console will automatically register eligible Android apps to meet Android developer verification requirements that start September 2026. After that date, apps must be registered under a developer with a verified identity to remain installable on certified Android devices.

What the video covers (features + workflow)

• No separate account needed: You don’t need to create an additional account in Android Developer Console; registration is handled inside Play Console.
• Expected coverage: Play expects to automatically register up to ~98% of Play apps using existing Play Console information.
• Post-run email summary: After auto-registration runs for a developer account, you receive an email showing how many apps were:
  • automatically registered
  • not automatically registered
• In-Console status visibility:
  • On the Play Console homepage, each app shows a package name status indicating whether it was successfully registered.
  • You can filter to view only unregistered apps.

How Play decides eligibility for auto-registration

Auto-registration applies when:

• The developer has a verified developer identity (all outstanding verification requirements completed in Play Console).
• The app’s signing key demonstrates ownership of the package name, using “package name eligibility rules” intended to reduce package name sharing and ensure the package belongs to its owner.

Signing key / ownership thresholds described

• If one signing key accounts for over 50% of known installs for that package, the app is automatically registered.
• If no single key has a majority, auto-registration happens if your key has at least 50 installs.
• The full eligibility rules are referenced as available in Play’s Help Center (link mentioned in the description).

When auto-registration fails (~2% of apps)

If an app isn’t auto-registered, it will require an additional/manual verification step to remain installable from September 2026.

Examples cited:

• Your key doesn’t meet the install thresholds.
• The app is in draft, so it has no associated package name.

What happens for unregistered apps

• A draft package name entry is created on the Android developer verification page.
• You then complete a manual ownership verification step by proving ownership of the app’s private signing key.

A separate “detailed video guide” is referenced for the manual package name registration process.

Important additional actions recommended

• Register any extra signing keys used outside of Play, so key/package pairs remain recognized.
• Register apps distributed outside Google Play as well—Play emphasizes that all apps distributed on Android (including non-Google Play channels) must have registered package name + key pairs to remain installable on certified devices from September 2026.
• You can register these within Play Console without creating a new Android developer console account.

Where to check / next steps (as instructed)

• Check the Play Console homepage for the auto-registration summary/status per app.
• Go to the Android developer verification page in Play Console to complete registration for apps that were not auto-registered.

Main speaker(s) / sources

• Google Play / Android developer verification team (Play Console product narrator) (no individual person named in the subtitles)