Troubleshooting 4 Min Read

Fix: Google Play Closed Test Not Starting

Even with 12 testers, your 14-day countdown might not trigger. Here’s why and how to fix it.

One of the most frustrating experiences in the Google Play Console is having your 12 testers ready, but seeing the "14-day record" not incrementing. You've sent the invites, they've accepted, yet nothing happens.

1. The "Opt-In" Link Trap

Simply adding an email to the list isn't enough. Testers MUST click the web opt-in link or the Android opt-in link. If they don't explicitly "Join on the web" or "Join on Android," they don't count towards the active testers list.

2. App Version Synchronization

Google Play requires testers to be on the latest version of your app. If you just pushed an update and 10 testers are on Version 1 and 2 are on Version 2, the status might remain stagnant.

3. The "Silent" Review Period

Did you know your closed test track itself needs to be reviewed? Whenever you add a new app version to the track, it enters a review state. Until the review is complete, the testing period doesn't technically "start" in Google's eyes.

  • Check Track Status: Ensure it says "Active" and not "In Review."
  • Tester Emails: Verify that testers are using the same email on the Play Store as the one you invited.
  • App Activity: Remind testers to actually perform an action in the app, not just open the splash screen.

4. Geographical Constraints

Sometimes, Google Play restrictions prevent testers in certain countries from downloading specific apps. Ensure your testers are in countries where your app is "available" in the app settings.

Conclusion

Persistence is key. If you are struggling to maintain 12 active testers, consider using a specialized platform like SwapTest to automate the matching process with reliable partners.

Get Reliable Testers Instantly

Stop chasing friends. Start matching with pro developers.

Join 12Tester Community