App Stuck in Google Play Closed Testing? Here's How to Get Unblocked

You built your app, uploaded it to the Google Play Console, set up closed testing... and nothing. Weeks go by and the app is still stuck, with no permission to move to production. This is one of the most frustrating problems for Android developers in 2026. Here's why it happens and how to fix it.

Why is your app stuck?

Google created closed testing to make sure new apps have a minimum base of testing before they go live to millions of users. But the requirements are stricter than they seem.

For Google to "release" your app, all of these criteria have to be met at the same time:

• 12+ valid testers (not just opt-ins)
• 14 consecutive days of real usage
• Devices that pass the Play Integrity API
• Google accounts that are active and genuinely in use
• An app with no critical crashes (Android Vitals)

If any one of these criteria fails, the cycle doesn't complete and the "Apply for production access" button never appears.

The 6 most common scenarios (and how to solve each one)

1. "I have 15 testers but the Console shows only a few opt-ins"

Adding someone to the tester list is not the same thing as that person accepting the invite. The flow is: you add them → they get a link → they click and accept (opt-in) → they install the app → they use the app.

Solution: Send clear step-by-step instructions to each tester. Confirm individually that each one completed every step. Track it daily in the Console.

2. "The 14 days passed but it didn't release"

Google counts 14 days of active usage, not just 14 days since the first opt-in. If testers installed on day 1 and only opened the app again on day 14, Google may not consider the cycle valid.

Solution: Create a daily testing script. Send reminders so testers use the app for at least 5-10 minutes a day, exploring different features.

3. "I used Telegram testers and it didn't work"

Telegram tester groups are the most common trap. Most of them use fake, freshly created, or shared accounts. Google detects this and silently discards them.

Solution: Drop the Telegram testers and start over with real testers. Read our article on why Telegram groups don't work.

4. "The app has crashes and the Console shows warnings"

Android Vitals monitors your app's health during closed testing. If the crash rate goes above 1.09% or the ANR rate goes above 0.47%, Google can block production access even if your tester cycle is fine.

Solution: Fix the crashes, publish a new version to closed testing, and wait for testers to use the updated version. Android Vitals recalculates based on the last 28 days.

5. "I filled out the production form and it got rejected"

The production access request form is the final barrier. Generic answers ("I tested it and it worked") or answers inconsistent with your Console data are grounds for rejection.

Solution: Fill it out with specific details — cite the number of testers, the devices used, and the bugs found and fixed. See our complete guide on the production form.

6. "I've tried everything and I still can't get out of closed testing"

If you've been trying to complete closed testing for more than 30 days without success, the problem is usually a combination of invalid testers and an interrupted cycle. Every failed attempt burns 14+ days.

Solution: Use a professional service. TestApps US runs the full cycle in 14-20 days, with real testing documented on physical devices.

Comparison: doing it yourself vs. a professional service

Frequently asked questions

← Back to the blog