Guide summary
Understand the September 30, 2026 Google Play app registration deadline, which packages need review and how to avoid global Play removal.
For: Google Play account owners, portfolio managers and release teams responsible for existing or newly created package names.
Release sequence
- Open Play Console Home and the Android developer verification area for the account.
- Identify packages that were not automatically registered and assign an account owner.
- Complete any requested package-name or signing-key ownership proof.
- Recheck the package and production certificate before the deadline.
Quick facts
Do not confuse the Play Console package-registration deadline with only the four-country store-install rollout. Google describes a Play-specific global removal consequence for packages left unresolved.
Detailed guidance
Audit Play Console by account
Google says more than 99% of Play apps were registered automatically, but that still leaves portfolios with unresolved packages. Review each developer account rather than sampling only active releases.
For an unresolved package, determine whether Play asks for package details, a signing-key ownership challenge or another account action. Capture completion evidence and verify the production certificate through the status API.
- Review Play Console Home for every account.
- Include dormant apps that must remain available for updates.
- Finish ownership proof before September 30, 2026.
Frequently asked questions
Is the deadline only for the four initial countries?
Google's Play Console guidance says remaining Play packages should be registered by September 30 to avoid global Play removal, which is a distinct consequence from the initial regional store rollout.
Are new Play apps registered automatically?
Current official guidance says creating a new Play app automatically registers and links its package name, subject to package-name availability.
Sources and review
Last reviewed: