Short answer: Yes. Google Play now has a separate app registration deadline, and unregistered Play packages can be removed after September 30, 2026. That is distinct from the closed test rules for new personal accounts.
Yes. Google Play now says Play apps must be registered in Play Console, and apps that are not registered by September 30, 2026 can be removed from Google Play. That deadline is separate from the closed test requirement for new personal developer accounts.
The part people get wrong is thinking there is one single deadline that controls everything. There are at least two different rules here. One is about whether your app package is registered in Play Console. The other is about whether a newly created personal account has completed the closed test needed before production access is available.
For package registration, Google’s current Play Console Requirements and Registering Play package names help pages say developers must register their Play apps, that most apps were auto-registered, and that remaining apps should be registered to avoid removal from Google Play. The policy deadlines page lists September 30, 2026 as the effective date for Play Console Requirements.
For testing, Google says personal developer accounts created after November 13, 2023 need a closed test with at least 12 testers opted in continuously for 14 days before production access can be requested. That requirement does not replace app registration, and app registration does not replace the testing rule.
The inconvenient part is that an app can be blocked for different reasons at different points in the release path. If a package is not registered, Google says it can be removed from Play. If a new personal account has not completed the closed test, the Production track stays disabled until the testing requirement is met. Those are different gates, and you have to clear both when they apply to your account and app.
If you maintain more than one app, check each package in Play Console. Google says you should review the Home page and register any remaining apps you want to keep distributing. Do not assume that one app being compliant means the rest are covered automatically.
If you are shipping outside Google Play as well, Google also says Play Console can register apps distributed outside Google Play so they can be installed on certified Android devices. That is a separate use case, but it uses the same registration concept, so it is easy to miss if you only think about Play Store publishing.
A practical way to read the policy is this: if your app is already on Play, confirm that the package is registered. If you are a personal developer account created after November 13, 2023, also confirm that your closed test has the required 12 testers for 14 continuous days before you plan a production submission.
If you are setting up a test workflow for a new app, DevConnect can help you find testers for genuine mutual testing, and it is free to use. It does not change Google’s rules, but it can help you organize the testing work you already need to do.
The safest assumption is simple: app registration is now a real release requirement, not just a housekeeping task, and it sits alongside the separate testing rules. Ignore either one, and distribution can stop working for that app or that account path.
What to do next
- Open Play Console and check the Home page for any apps that are not registered. Google says the Home page shows registration status.
- If you use a personal account created after November 13, 2023, confirm your closed test has at least 12 opted-in testers and that they have stayed opted in for 14 continuous days.
- If you see multiple apps, verify each package individually. Do not assume one app registration covers the rest.
- If your release plan depends on production access, treat registration and testing as separate checkpoints, because Google does.
What happens if you get it wrong
If you miss the package registration deadline, Google says the app can be removed from Google Play. If you miss the closed testing requirement, the Production feature remains unavailable until the requirement is satisfied. The result is the same for you either way: you do not get a clean path to distribution until the missing step is fixed.
Concrete example
A personal developer account created in 2025 can have a registered app package and still be unable to publish if the closed test has only 10 opted-in testers. The reverse is also true: a closed test can be complete, but if the app package has not been registered by the deadline, the app is still at risk of removal.
Bottom line
Yes, app registration in Play Console now matters as a distribution requirement. No, it is not the same thing as the testing rule, and it does not cancel that rule. Treat them as separate checks, because that is how Google documents them.
Frequently asked
Does app registration replace the 12 tester closed test requirement
No. Google documents app registration and closed testing as separate requirements. A registered package can still be blocked from production access if the closed test requirement is not met.
If my app was already on Google Play, do I still need to check registration
Yes. Google says most apps were auto-registered, but developers should check Play Console and register any remaining apps they want to keep distributing.
What date matters for app registration removal risk
Google’s Play Console Requirements page lists September 30, 2026 as the effective date for the registration requirement it describes.
Does internal testing count toward the closed test requirement
No. Google says internal testing allows up to 100 testers and does not count toward the closed testing requirement.
Sources
- Play Console Requirements
- Policy Deadlines
- Registering Play package names
- App testing requirements for new personal developer accounts
- Check your app’s policy status
- Create and set up your app
Originally published at devconnectplatform.com, where it is kept up to date.
