Google Play Pre-registration Disabled? The 12-Tester Lock

Short answer: why the Pre-registration page is disabled

Google gates pre-registration behind the same testing requirement it gates production with. In the Play Console Help article written for new accounts, the sentence is explicit: “Certain features in Play Console, such as Production (Test and release > Production) and Pre-registration (Test and release > Testing > Pre-registration), remain disabled until developers meet these testing requirements.” For a personal developer account created after November 13, 2023, those requirements are a closed test with at least 12 testers who have been opted in continuously for the preceding 14 days.

The same lock is described a second time in Google's app dashboard article: personal accounts created after 13 November 2023 “must meet specific testing requirements before they can access production to release their app on Google Play, or use other features such as pre-registration or open testing.” Both documents were checked on October 21, 2026.

What does Google Play pre-registration actually do?

Google defines it as a way to “build excitement and awareness for your apps and games in countries that you select before you publish them on Google Play.” Your store listing goes live early with a Pre-register button instead of an Install button. When you later publish on the production track, “all pre-registered users receive a push notification from Google Play to install it,” and eligible devices “have the app or game auto installed on the day it launches.”

• It is a public listing, not an invite list. Anyone who finds the listing in a country you selected can pre-register. You control countries and supported devices, not a roster — the way you control a closed test with an email list or a Google Group.
• It is capped at 90 days. Google's setup article states that “pre-registration campaigns can only last 90 days, after which you need to launch your app to production.”
• It is capped at two apps. “You can make up to two apps or games available for pre-registration at a time.”
• Auto install has device conditions. The user needs an Android M+ device with Play Store version 19.2 or newer, and app size matters: bundles up to 200 MB can auto install over Wi-Fi or cellular, up to 2 GB on Wi-Fi only, and above 2 GB auto install is not available. Children's accounts and managed enterprise accounts are not eligible.
• Countries follow the Play account, not the person. Google notes that pre-registration countries are “the countries or regions where the user is registered on Google Play, not their physical location.”

What unlocks at each stage for a new personal account?

Play Console releases its features in a fixed order, and pre-registration sits at the far end of it, next to production. Google's testing requirements article lists the purpose and the access requirement for every track:

• Internal testing — no requirement at all. It works before your app setup is complete, and builds are “normally available to testers within seconds.” It does not count toward the 12.
• Closed testing — the only requirement listed is completed app setup. This is the track the 14-day clock runs on.
• Open testing — requires production access first. Google states that “open testing becomes available after you gain production access.”
• Production — requires the closed test plus an approved application.
• Pre-registration — named in the same sentence as Production as a feature that “remain[s] disabled until developers meet these testing requirements.”

One honest gap in the documentation: Google's approval section describes what happens when your application is accepted — “you can access your app's Production page (Test and release > Production) and distribute your app to users on Google Play. You can also access Open testing” — and does not describe the Pre-registration page's state at any specific step. Google ties pre-registration to meeting the testing requirements, not to a documented screen-by-screen unlock. If a launch date depends on the exact day the page appears, plan around production access approval and re-check the left menu after your review completes.

Can pre-registration replace the closed test?

No, and the dependency runs in the opposite direction to what most developers assume. Pre-registration is locked behind the closed test, so it cannot be used to avoid one. It also cannot end anywhere except production, because Google's rule is that a campaign “can only last 90 days, after which you need to launch your app to production” — and production itself requires the closed test, the 12 opted-in testers and an approved application.

Google's own ordering advice matches that dependency: “We strongly recommend rolling out a release to a test track and testing your app before starting pre-registration.” The bundles you upload on the pre-registration track are not a distribution channel either — Google states that app bundles uploaded there “are only used to specify your supported devices, and won't be released to users.”

How do pre-registration and a closed test interact in the same country?

This is the part almost nobody reads before turning pre-registration on, and it is fully documented in Google's pre-registration article under “Testing during pre-registration.” Three rules decide what happens if the two overlap in one country.

• Your testers cannot pre-register while they are testing. Google states that “users who have already joined your tests will not be able to pre-register until they uninstall and opt out of the testing program for your app.” A tester who opts out to pre-register is a tester who is no longer opted in — during your 14 days that is a dropped tester, not a marketing conversion.
• The listing flips for everyone else. If you switch a country to pre-registration while running a test there, existing test users “continue to receive updates released on their respective testing track,” while other users “will see a Pre-register button instead of an Install button on your store listing.” For open tests specifically, new users can no longer join from the listing, but they can still join through the opt-in URL.
• The launch notification gets spent early. If pre-registration is on in a country and you then release a test in that country, opted-in test users “receive the pre-registration notification asking them to install. They will not receive a subsequent notification after you launch your app or game in production.” The one message Google sends arrives during your test, not on launch day.

Two practical consequences. First, your 12 closed testers are not your launch-day audience: Google separately notes that “users who already have a test version of your app installed won't receive a push notification” when the production launch happens. Second, if a pre-registration campaign is part of your plan, keep it out of the countries where your closed test is running, and keep your testers opted in until the window closes. The same article gives the closed-test opt-in URL format for reference: https://play.google.com/apps/testing/your.package.name.

What happens if the 90 days run out?

The limit is hard, and the consequence is worse than a pause. Google's warning: “If you haven't launched within 90 days in any of these countries, your pre-registration campaign will be terminated in all countries and new pre-registration campaigns can't be started.” The clock is tracked per country — “the 90-day window for a country starts when you make pre-registration available in that country for the first time” — but missing it in one country ends the campaign everywhere and locks you out of starting another.

Google's timing guidance is to turn pre-registration on three to six weeks before your planned launch date, and to do it before you start the marketing campaign rather than after. Working backwards from that, and forwards from a closed test that needs 14 days plus a production access review that Google says “usually takes seven days or less, but can occasionally take longer,” the pre-registration page should be available several weeks before any realistic launch date — provided your 12 testers stayed opted in.

What to do while the Pre-registration page is locked

The lock is a sequence problem, not a settings problem. The work that moves it:

1. Finish app setup. Google states that “you can start a closed test after completing your app setup,” so the closed track itself is unavailable until the Dashboard tasks are done.
2. Run the closed test and watch the count. 12 testers opted in, continuously, for the preceding 14 days. A Dashboard that reads 0 opted in means invitations were sent but nobody completed the opt-in.
3. Apply for production access from the Dashboard. If the button is not there yet, the causes are limited and checkable, and the form itself asks about recruitment, engagement, feedback and the changes you made.
4. Wait out the review. An email goes to the account owner when it finishes, usually within seven days.
5. Then plan pre-registration backwards from launch — three to six weeks of campaign, inside the 90-day cap, in the countries where you intend to launch production.

Based on our analysis of 1,500+ closed-testing campaigns, the delays that cost developers the most time are sequencing ones rather than technical ones: a launch date is planned around a pre-registration campaign that cannot start until the closed test is finished and production access is granted. That is our own campaign record — closed tests we have run and tracked — not Google's data. Build the timeline backwards from the day production access realistically lands, not from the marketing date.

Frequently asked questions

Does a pre-registration campaign count toward the 12 testers? No. Google's requirement is written only about a closed test — “developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days.” Pre-registration is a launch and awareness feature, listed separately from the three testing tracks, and it has no tester roster to opt in at all.

Can I start pre-registration before my closed test is finished? No. Both Google sources tie pre-registration to the same testing requirements that gate production, and the pre-registration article repeats it: new personal accounts “must meet specific testing requirements before they can make their app available on Google Play and, by extension, before they can use pre-registration.”

Will my 12 testers get the launch notification? Usually not. Google notes that “users who already have a test version of your app installed won't receive a push notification,” and in the overlap case the notification is spent when the test is released in that country, with no second message on production launch.

Can testers and pre-registration run in the same country? Yes, with the consequences above. Existing testers keep their track's updates, new users see a Pre-register button, and testers who want to pre-register must first uninstall and opt out of the test — which ends their contribution to your 14 days.

What happens if I do not launch within 90 days? The campaign is terminated in every country, and Google states that new pre-registration campaigns can't be started afterwards. A paused (inactive) campaign does not stop the clock: “the 90-day limit still applies.”

How many pre-registration campaigns can I run at once? Two apps or games. Beyond that, and beyond the content declarations Google requires before pre-registration can be switched on, the 12-tester lock itself is written only about personal accounts created after November 13, 2023, and the requirement does not apply to organization accounts.

Is there anything else that has to be ready before the page works? Yes. Google states that “you won't be able to use pre-registration until you provide some information about your app's content,” the same app-content work your closed test and production access application depend on. Completing it early is free, and it removes a second lock after the testing one opens.