TestAppsGoogle Play Closed Testing Won't Complete? 5 Reasons and How to Fix It
You set up closed testing in the Google Play Console, added testers, waited 14 days... and nothing happened. The cycle won't complete, the testers don't show up, or Google simply won't unlock the production form. This is one of the most common problems among Android developers in 2026.
1. Testers with Google accounts that have no history
Google doesn't count just any account as a valid tester. The Play Integrity API evaluates account signals on the Play Store — previous downloads, ratings, account age.
Recently created accounts (less than 30 days old) or accounts that have never downloaded any app are often silently ignored. This means that even with 15 people in your closed test, Google may be counting only 5 or 6 as valid testers.
How to fix it
- Use only Google accounts with real Play Store history
- Ask testers to have at least 3-5 apps installed via the Play Store
- Avoid corporate accounts (Google Workspace) with no personal Play Store use
2. Testers didn't opt in correctly
There's a difference between adding someone to the tester list and that person accepting the invitation (opt-in). Many developers confuse the two.
The correct flow is:
- You add the tester's email in the Google Play Console
- The tester receives an invitation link
- The tester accepts the invitation by clicking the link
- The tester installs the app via the Play Store
- The tester uses the app during the cycle
If the tester only accepts the invitation but doesn't install or use the app, they don't count. Google needs to see real usage — sessions with a minimum duration, interactions with the interface, navigation across different screens.
How to fix it
- Send clear instructions to each tester (step-by-step with screenshots)
- Confirm individually that each person opted in and installed the app
- Monitor the number of active opt-ins in the Console daily
3. Uncertified or rooted devices
The Play Integrity API (the replacement for SafetyNet) verifies the device at three levels:
- Basic integrity — the device is not compromised
- Device integrity — it is a Google-certified device
- Strong integrity — locked bootloader, no modifications
Devices that are rooted, have an unlocked bootloader, custom ROMs, or emulators do not pass the check. Tests run on these devices are silently discarded.
How to fix it
- Use only factory-original Android devices (Samsung, Motorola, Xiaomi, etc.)
- Check that the device passes the integrity test (apps like “Play Integrity API Checker”)
- Avoid very old devices (Android 8 or lower may have problems)
Tired of cycles that never complete?
TestApps US runs the complete cycle with real human testers on certified physical devices. Real testing, documented across the entire cycle.
Fix it now →4. Cycle interrupted before the 14 days
Google counts 14 consecutive days of active usage. If testers stop using the app for a few days in the middle of the cycle, the counter can be reset. It's not enough to install on day 1 and open it again only on day 14.
Google looks at:
- How frequently the app is opened over the 14 days
- Average session length per opening
- Diversity of flows navigated (just opening and closing isn't enough)
- Usage spread across different times and days
How to fix it
- Create a testing script for testers to follow every day
- Send daily reminders (WhatsApp or email) to keep engagement up
- Document which flows should be tested each day
5. App version with bugs or crashes
If the app crashes frequently, Google logs this in the Console and may consider the testing cycle insufficient. Android Vitals monitors:
- Crash rate — if it exceeds 1.09%, the app is flagged
- ANR (App Not Responding) — if it exceeds 0.47%, it's flagged
- Startup time — slow apps are penalized
Even if the 14-day cycle completes, an unstable app can be rejected on the production form with the reason “the app does not meet quality standards”.
How to fix it
- Monitor Android Vitals in the Console during the cycle
- Fix critical crashes immediately and publish a new version to the closed test
- Test the app on low-memory devices (2GB RAM) before starting the cycle
Summary: checklist before starting closed testing
- ✓ 12+ testers with real, active Google accounts
- ✓ Everyone opted in AND installed the app
- ✓ Certified physical devices (no root/emulator)
- ✓ Testing script defined for the 14 days
- ✓ Stable app — no critical crashes
- ✓ Updated version with an appropriate targetSdkVersion
- ✓ Daily Console monitoring
Frequently asked questions
Why don't my testers show up in the Google Play Console?
Google can take up to 48 hours to register the opt-in. In addition, newly created accounts or accounts with no Play Store history may be silently ignored.
Does closed testing have to be exactly 14 days?
It's a minimum of 14 consecutive days. If testers stop using the app during the cycle, Google may consider the period insufficient and require you to start over.
Can I use an emulator for closed testing?
No. The Play Integrity API detects emulators and virtual machines. Only certified physical devices are accepted by Google.
How many testers do I really need?
The official minimum is 12 testers with an active opt-in. In practice, 14 to 20 is recommended, since some may be discarded by Google if the accounts don't have enough history.
What happens if closed testing fails?
You can restart the cycle with new testers. There's no penalty, but each attempt takes another 14 days. The key is to use real testers on physical devices.
Leave closed testing to the experts
TestApps US has already helped more than 800 apps pass closed testing on the first cycle. Human operators, certified devices, complete evidence.
Talk to TestApps US →