Two clocks are running toward the same date. On September 30, 2026, Google Play expects every app you still want to distribute to be registered in Play Console under Android developer verification. Google says about 99% of apps on Play were registered automatically — but the leftover 1% is the part that can disappear. This tutorial walks a Play developer through confirming identity, reading the Home page for unregistered packages, registering what is left, and understanding the separate install-time protections that start the same day in four countries.

What you are solving today: Play Console Requirements plus Android developer verification. Unregistered Play apps risk global removal from Google Play. Separately, starting September 30, 2026, installs from participating stores in Brazil, Indonesia, Singapore, and Thailand are checked against a verified developer. Do the Play Console work first; that is where most Play developers already live.

What September 30 actually changes

Google’s Preview: Play Console Requirements (July 2026 policy updates) is explicit: to meet Android developer verification and Play Console requirements, you must register your Play apps in Play Console. Check the Play Console Home page and register any remaining apps you want to keep distributing, so you avoid global removal from Google Play and keep a normal install path for users. The same Help article notes you can also register apps you distribute outside Google Play so they can still be installed on certified Android devices.

The Android Developers guide Register on Google Play Console repeats the 99% auto-registration figure and the September 30, 2026 cutoff, and adds the ownership detail that matters in the leftover cases: registering a package name may include proving ownership of the private signing keys used for those packages.

That Play-catalog deadline is not the same thing as the regional install check — but they share a date. Treat them as two checklists, not one blurry “verification” task.

The other September 30 clock: participating stores in four countries

Android Developer Console Help describes a separate protection layer. Starting September 30, 2026, developer verification protections go live for users in Brazil, Indonesia, Singapore, and Thailand. In that first wave, the system verifies installations from these participating stores:

Help for that program says apps from developers who have not verified identity and registered apps by the deadline will be unavailable for new installation on certified Android devices in those countries. A later global expansion is planned for 2027. Play developers should still start in Play Console — that is the registration surface Google documents for Play package names.

Step 1 — Confirm your identity in Play Console

Android Developers is blunt: for most Play developers, no new identity action is required. The identity you already completed for Play’s developer verification usually satisfies this program. Confirm it instead of re-doing it:

  1. Sign in to Google Play Console as the account owner (or an admin who can see developer-account settings).
  2. Open Settings.
  3. Open Developer account (the Android Developers guide says “Developer Account on the Settings page”; Play Console Help for registering Play package names points at Settings > Developer account).
  4. Read the current verification / account-information state. If identity verification already succeeded, Play Console Help says you do not go through that step again.

Play Console Help on Registering Play package names also notes a practical catch: you only receive Home-page notifications about registration status after identity verification is complete. If Home looks silent, finish or confirm identity first — do not assume every package is already clean.

Step 2 — Read Play Console Home for unregistered packages

Do not trust the 99% headline for your catalog. Official guidance is to look at Home:

  1. Open Play Console Home.
  2. Look for the registration-status notice above the app list (Play Console Help describes this placement).
  3. Open the Android developer verification page from that notice (or from Settings) to see per-app registration status.
  4. Write down every package that is not fully registered — including drafts created for leftover Play apps that were not auto-registered.

If every package name was auto-registered, Play Console Help says no further registration action is required for those Play apps. You can stop the Play-catalog part of this tutorial and, if you also ship APKs outside Play, continue to Step 4.

Step 3 — Register the leftovers (and prove the signing key when asked)

Google tries to auto-register existing and new Play apps using package-name eligibility rules (majority signing key by known installs, keys with 50+ installs when no majority exists, and first-come rules under 50 installs). New apps created in Play Console are registered automatically and linked to your account; if the name is already taken on Play, Console asks you to pick another.

When auto-registration missed a package, Help says you can register it manually. The documented Play Console path is:

  1. On the list of apps that still need work, hover each row and follow the on-screen guidance.
  2. Choose Add key.
  3. From the list of eligible public certificates, select your app’s certificate and add that key.
  4. Choose Get Started to sign and upload an APK. Play Console gives you a snippet to copy into an APK assets folder, then you sign that APK and upload it. Help links a sample project so you can see the required file structure. The same article notes you do not need to upload the actual production APK — the signed proof APK is the ownership check.
  5. Wait for the email that the package name registered, and re-check status on the Android developer verification page.

That upload is how you prove ownership of the private signing key for a package that was not auto-linked. If your key is not eligible under the install-share rules, Help says you must submit a request to use the package name. Unless you have a legitimate reason to share that name, Google recommends adopting a new package name instead of fighting an ineligible key.

Step 4 — Register off-Play packages you still want on certified devices

Play Console Requirements and the Android Developers Play Console guide both say you can use Play Console to register apps you distribute outside Google Play, so they remain installable on certified Android devices. That is optional for a Play-only catalog, and required thinking if the same package also ships through HONOR, OPPO, Galaxy Store, Palm Store, V-Appstore, GetApps, or your own site — especially for users in the four-country first wave.

If you have no Play Console account and only distribute outside Play, Android’s program documents a separate Android Developer Console path. That is out of scope for this Play-developer tutorial; start from the Android Developers verification guides, not from a second Play listing.

What you lose if a package is still unregistered on September 30

There is no official “grace weekend” in the articles cited below. If Home still shows leftovers, register them before the cutoff rather than waiting for a removal email.

A 10-minute checklist

  1. Confirm identity under Settings → Developer account.
  2. Open Home and read the registration notice above the app list.
  3. Open Android developer verification and list every unregistered package name.
  4. For each leftover: add an eligible signing key and complete the signed-APK ownership step, or file a request / change package name if the key is ineligible.
  5. If you ship the same packages outside Play, register those names too.
  6. Keep the owner’s Google Account on 2-Step Verification so the person who can finish this work is not locked out on September 29.

The one-line version

By September 30, 2026, every Play package you still want live must be registered to a verified developer: most Play identities already count, about 99% of packages were auto-registered, and the work is to check Home, register the rest (proving the private key when asked), and avoid global Play removal — with a parallel install check the same day on participating stores in Brazil, Indonesia, Singapore, and Thailand.

Sources