Guide summary
Check the Android developer verification scope in effect since September 30, 2026 and the steps to remediate unresolved package registration.
For: Release managers checking whether a package is in the first enforcement footprint and how to remediate an unresolved registration now.
Release sequence
- Check whether users install the app through a participating store in Brazil, Indonesia, Singapore or Thailand on certified Android devices.
- Open the relevant developer console and verify identity and package-name registration status.
- For each distributed artifact, compare its production package name and signing certificate fingerprint with the registered values.
- Route unresolved packages to the account owner, and track Android's broader 2027 rollout separately from current regional scope.
Quick facts
The date has passed, but it was not a universal sideloading ban. Android scopes the first phase to participating stores in the four named countries on certified Android 7 or higher devices; ADB remains unchanged, and advanced flow is the separate path for unregistered sideloads. Check a specific Play account for its separate package-registration task.
Detailed guidance
Check the current scope and unresolved work
Android's first phase began September 30, 2026: installations from seven named participating stores on certified Android 7 or higher devices in Brazil, Indonesia, Singapore and Thailand. This date is not a universal block on sideloading. Android says ADB remains unchanged and unregistered sideloading can use the advanced flow, with a different user experience.
For each affected listing, check its own account task, production package name and delivered certificate. Google Play's separate package-registration help states that unregistered Play apps will be removed from Play; the regional store scope does not establish an individual app's current Console status.
- Regional scope: four countries, named stores and certified Android 7+ devices.
- Play scope: check every account's Play Console Home for remaining package tasks.
- Future scope: Android says broader global expansion is planned for 2027 and beyond.
Have the production package name and signing certificate ready? Query the official registration state, then use the result to choose your next step.
Run status check →Frequently asked questions
Has the September 30 date passed?
Yes. Android's first regional phase began on September 30, 2026. If an affected package remains unresolved, inspect the account console and the exact artifact certificate rather than relying on a countdown or a package-only result.
Does the first phase block all sideloads or ADB installs?
No. Android limits the first phase to installations from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices. Its current guide says ADB remains unchanged and unregistered sideloading can use the advanced flow.
Sources and review
Last reviewed: