Menu
The new iTunes Connect distinguishes between the internal testers (maximum of 25) and external testers (maximum of 1000).
At various points they say that newly uploaded builds are automatically distributed to internal testers via the test flight app, and this has usually been my experience. But sometimes I see a menu like this, indicating that I need to select "Invite Testers" in order for it to be visible to internal testers:
What causes this?
When it does this, I cannot distribute my build to my internal testers, and it seems like iTunes Connect is failing to recognize that my project already has internal testers.
940
To add an internal tester, head to the Users and Access section in App Store Connect. For this example, use your own email address. If you were adding other internal testers, you'd use their email addresses and they would carry out the steps of accepting an invitation. Click the + button to add a new user.
External testers and groups. Invite up to 10,000 external testers using their email addresses or by enabling and sharing a public link, which creates an open invitation for anyone to test your app. Simply create a group of testers and add the builds you'd like them to test.
We've been experiencing this too. A hack that works for us sometimes is turn the TestFlight Beta Testing switch off, then wait for that to take effect, then turn it back on, and it usually pushes the latest out to the internal testers.
55
Turning the "Test Flight Beta Testing" switch off and back on will indeed change the "Internal" column to Active. As @will suggests. The problem is that if you are already approved for External delivery, this will also cause the external testers to go back to the Submit For Beta App Review again, so use this work-around with care.
26
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
