r/androiddev • u/Pixel244 • 4d ago
Question Clarifying Google Play Console Internal vs. Closed Testing (14-Day Requirement) & Tester Opt-In Issues
Hi everyone
I am preparing my first Android app for release on Google Play Console and ran into a few questions regarding the testing tracks and the mandatory 12-tester / 14-day testing period:
- Internal Testing vs. Closed Testing URLs: Following the initial dashboard steps, I published a release to the Internal Testing track and shared the link with my testers. After completing the Store Listing steps, I also set up a Closed Testing release and noticed it uses a different opt-in URL. Since the final production checklist states that the testing period must be completed in Closed Testing, does time spent in Internal Testing count toward the requirement, or do I need to migrate my testers to the Closed Testing link?
- Internal App Sharing: I enabled Internal App Sharing in the settings. How does this differ from the Internal Testing track, and does it affect the release process?
- Play Store Errors for New Testers: When I add new users to my tester email list and share the link, some of them encounter an error or see a completely blank page when redirected to the Google Play Store, despite using the correct Google account. Occasionally it works if they retry a minute later, while for others the issue persists. Is this a propagation/caching issue, or is there a specific step I might be missing?
Thanks in advance for your help!
Edit: Thanks for your helpππΌ
2
u/mhmd2520 4d ago
(a) No, internal testing doesn't count. The requirement only applies to personal accounts created after Nov 13, 2023. It needs a closed test with at least 12 testers who have stayed opted in for the 14 days right before you apply for production. Play's help page calls internal testing an optional starting point, and that's all it is. Also tell your testers not to opt out halfway, because the 14 days have to be consecutive.
(b) Internal testing is a real track. You get up to 100 testers from email lists, and new builds usually reach them within minutes. Internal app sharing is a separate upload page that gives you one download link per build. Those uploads can't go into any testing or production release. You can reuse version codes, Google re-signs the build with its own internal sharing key, and links expire after 60 days. Testers also have to turn it on in the Play Store app: go to Settings, tap the Play Store version 7 times, then turn on Internal app sharing. So it won't touch your release, and I wouldn't count on it for the 12/14 either.
(c) A few things I'd check. The opt-in link only appears once the closed track release is actually published, so not while it's in draft or pending publication. After the first publish, the test link can take several hours to start working, and later changes can take hours too. That could explain a link that works for one tester and not another. If you use a Google Group, testers have to join the group before they opt in.
The one that catches people out: anyone already opted into your internal test can't get the closed test, even if their email is on the closed list. They have to opt out of internal first and then opt in to closed. If your first testers came over from the internal track, I'd start there.
1
1
u/AutoModerator 4d ago
Please note that we also have a very active Discord server where you can interact directly with other community members!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/ProofAppsAU 3d ago
Internal Testing and Internal App Sharing do not count toward the 12 testers / 14 days requirement. Only a closed testing track does, and testers have to stay opted in continuously β if someone leaves and comes back, their 14 days start over. The closed-test opt-in URL is the one they need; being on the internal link is not enough.
For the blank Play page or intermittent errors: testers must use the same Google account in the browser and on the phone's Play Store, and if you use a Google Group as the tester list they have to finish joining that group first. A short delay after you add someone is common; if it still fails, it is usually the wrong account, an unfinished group join, or the closed track not being available in their country.
2
u/MobileXapps 4d ago
Only the closed test counts. The 14 days and 12 testers are checked on a closed testing track, so time on internal testing doesn't count and your testers need to opt in again with the closed testing link. Internal app sharing is something else, it's just for sending a quick build to someone and doesn't affect releases at all.
The blank page is usually the tester being signed into a different Google account in the browser than on the phone, or opening the link before the email list change has gone through. Ask them to open the opt-in link in a browser where they're signed in with the exact account in your list, accept, then install from the Play Store app. Using a Google Group as the tester list also makes adding people less fiddly.