Reputation: 4025
I set up a build and add two Internal Testers. Immediately after pressing the "Invite" button I noticed that the checkbox next to my email address was the only one that remained checked. The checkbox next to the second tester was unchecked. So I clicked the checkbox and sent another invite, but the same thing happened. I thought nothing of it, figuring it would become checked when he actually installed and tested the app. But he says he never received an invite. Does anyone know if I'm doing anything wrong?
Upvotes: 30
Views: 40212
Reputation: 16427
For me, the problem was the internal tester had accepted the invite with a different Apple ID (and email address). Getting them to tap the "Stop Testing" button in TestFlight removed them from the test list.
I was then able to re-add the original tester and voila its working again.
Upvotes: 0
Reputation: 3218
I got the same issue. Fixed:
1) Under the TestFlight tab, click App Store Connect Users.
2) Select Edit at the top right.
3) Try removing a user.
4) Click the + icon next to the word "Testers" at the top.
5) Add the person you just removed.
That should work and send them an email with a link to test.
It should also give you the option to resend invite to that person now. I think it's ridiculous that you have to do this, but it worked for me
Upvotes: 7
Reputation: 1342
Note that the App Store account used to download the TestFlight app is also important! I have a french and a US App Store accounts. If I download TestFlight from the french store, TestFlight requests my Redeem Code (that can't be resent...) If I remove TestFlight.app, switch to US App Store account, download TestFlight then the app is automagically configured and I don't need to enter any redeem code.
Crazy! That's the first time i've seen an have that autoconfigures its default data based on the Store/Account it was downloaded from.
Upvotes: 0
Reputation: 3708
For me, none of the above solutions worked.
So I tried editing the "What to Test" under Test Details section after clicking the build no. and voila all the testers got the testflight email. Wasted hours on this.
Hope it helps someone.
Upvotes: 0
Reputation: 6895
Make sure that you've configured the internal testers and then follow the steps as illustrated in the image.
Note: Once you make a testing version available to internal users then any new build for that version would become available to testers upon uploading to iTunesConnect automatically.
Upvotes: 2
Reputation: 12582
Just some minor observations that may help, (Nov 2015)
(*) after turning on internal testing, and/or adding an internal tester, it does take some time for that person to get the crazy "CompanyName has invited you to test AppName" email --- maybe an hour. This is ridiculous, but that seems to be how it is
(*) indeed note that there is a ridiculous "CompanyName has invited you to test AppName" email. Again this is for INTERNAL testing. you'd think that after you click internal testing, the app would of course just pop-up inside TestFlight. But no. nothing happens until the person (often yourself!) gets that email and confirms in the email
(*) that person (even yourself) has to use the hilarious Redeem Code feature, before it finally appears in TestFlight. Again this is just for the internal testing
What a mess!
Upvotes: 11
Reputation: 10762
I've found that deleting and recreating the user solves the problem.
Upvotes: 5
Reputation: 1924
Check your External Testers list.
You can't have same email/tester exists in both Internal and External testers at the same time.
And, sometimes it does take a while to receive tester emails from Apple.
Upvotes: 20
Reputation: 1655
It is not as clear as the old TestFlight and I think it's still too many unnecessary hoops. Some quick questions...
Did you add them under "iTunes Connect Users" in Users & Roles? (I assume you did)
Under Users and Roles, did you add them under "TestFlight Beta Testers/Internal"?
After that you should be able to add them on the app.
I also think there is an issue where it will not allow you to add them if they don't have a valid device for the build (i.e. an iPad app and they only have an iPhone). It appears to be trying to be "helpful" by not showing you invalid devices and instead is just confusing.
G
Upvotes: 1