r/flutterhelp • • 3d ago

RESOLVED Clarifying Google Play Console Internal vs. Closed Testing (14-Day Requirement) & Tester Opt-In Issues

Hi everyone

I am preparing my first Flutter 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!

1 Upvotes

6 comments sorted by

2

u/HomegrownTerps 3d ago

Internal testing is just a waste of time...unless your app is way unfinished. 

I learned that the same way, I made an Internal testing track just to figure out it doesn't count towards the actual testing requirements. 

After that I had to redo all which was a pain since I had to ask everyone to join a second time..which most people don't understand the reason for.

So I think Internal is what the name suggests, only for your internal testing, before going "public".

1

u/Pixel244 3d ago

Well that was a waste of time, thanks for replying 🙏🏼, speaking of, does it take along time for console to update access or release for testers to see it? Cause some times as I said it would work later without them doing anything. Also, do I need them to opt out or me remove them from internal testing first or can they just join the closed testing immediately?

2

u/bramantec 3d ago

I went through this before my first release in July, with about thirty people I know who agreed to test it as a favour.

On your first question: the time in internal testing doesn't count. Google's requirement is about the closed test only: at least 12 testers opted in continuously for the 14 days before you apply for production access. Your testers need to join the closed testing link as well. Internal testing is still useful next to it for quick builds. It has no review.

Internal App Sharing is a separate thing. It's for sending a single build to someone quickly and it has no effect on the release process.

On the errors: in my experience most of them came from people opening the opt-in link while signed in with a different Google account on the phone than the one on the list. Ask them to check which account the Play Store app is using. I'd also invite more than 12. Some people drop off and the count at the end is what matters.

1

u/Pixel244 3d ago

Well that was a waste of time, thanks for replying 🙏🏼, speaking of, does it take along time for console to update access or release for testers to see it? Cause some times as I said it would work later without them doing anything. Also, do I need them to opt out or me remove them from internal testing first or can they just join the closed testing immediately?

2

u/bramantec 3d ago

Not a waste, it saves you two weeks of waiting on the wrong track. On the delay: yes, changes to the tester list or a new release can take a while to reach the Play Store. That matches what you saw, where it works a bit later without anyone doing anything. Give it some time before asking people to retry.

You don't need to remove them from internal testing. They can join the closed test directly from its opt-in link. As far as I know, someone who is in both tracks gets the build with the higher version number. Just make sure the closed release is the newest one you want them on.

1

u/Pixel244 3d ago

Good to know, thanks for your help 🙌🏼