Operational summary
Google reports that most Play apps were registered automatically, but developers must review Play Console Home and complete any remaining package registrations by September 30, 2026. This Play requirement is broader than the four-country first phase because unregistered Play apps can face global removal.
Recommended 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.
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
PkgReady summarizes operational implications but does not replace an official console or Android documentation. Reviewed 2026-08-14.