No TestFlight invite email gets sent for internal users

Question

I set up my application for TestFlight. For external users it is waiting for review. But if I want to invite internal users, I select them and press invite. iTunes Connects says they are invited now, but none of the invited emails gets an invitation email.

Do you know what I am doing wrong?

Answer 1

I had this issue, internal test not getting the invitation mail.

I desperation I thought that it might work if I added the tester as an external tester. But before I could add a tester as an external tester, I had to send the app for test review.

When the app was approved for testing, the tester, suddely got all the different invitations I had tried to send the day before. So then no need to add her as an external tester...

Answer 2

only users with permissions can be added as Testers

steps to follow.

1. https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/users_roles

2. https://appstoreconnect.apple.com/apps/1494800176/testflight/users

   Internal Group
           App Store Connect Users
   

Answer 3

This is what worked for me in November 2017.

1. Get the build approved by Apple for beta.
2. Add the approved build in #1 to an app submission and save.
3. Now you should see the resend invitation buttons in TestFlight > Builds: iOS under the External Testers column, or TestFlight > Testers & Groups: All Testers under the Status column for each tester.

I'm not sure what triggered the invite email to be sent to internal testers, as there was only a button for external ones, but soon after I did #2, I got an invite as an internal tester.

Also, as I didn't track this process too carefully, I may have triggered the solution by changing the marketing build version in my app submission (#2) to be the same as my beta build version.

Answer 4

Since the very recent new update to iTunes Connect, there is a prominent “Resend Invitation” button on all internal users who have not yet redeemed their invitation.

Answer 5

This is an issue with TestFlight. As a workaround,

1. Remove the existing testers
2. Save
3. Add them again

:)

Answer 6

Check your Trash/ Bin! All my 6 invites were automatically moved there because I unsubscribed from testing last week.

Answer 7

This seems obvious, but I didn't see a main reply with this solution. Make sure your app is in "Beta" status (already through Beta review by Apple). If it is still in Prerelease status but has no beta, external users will never get in invitation email.

Answer 8

The problem with inviting an internal tester is that you cannot have an internal and external tester with the same apple ID.

Although deleted and recreated the user in user roles I still had the same problem. When I removed the duplicate email from External Testers and went back to Internal Testers, the invite was sent.

Source : Check this SO link

Edit : I will still like to mention that when I tried it then I had to use an email which was not connected to iTunesConnect earlier. For some reason, Apple doesn't allow an existing iTunesConnect User to register as Internal Tester on Testflight and I don't have any explanation for this issue. I believe even Apple doesn't have an explanation and I assume its a major bug ;)

Answer 9

I tried it all, but none worked. Than I realise I was using a new email created for this sole purpose and hadn't used it in the App Store yet.

So the solution is simple:

1. Log in with your new Apple ID in the App Store.
2. You will be requested to finish your sign-up, filling info about address and title.
3. No credit card information is needed, just leave it as none.
4. After accepting the terms and log in in App Store, deselect the internal tester user in iTC, save it, select it again and then invite.
5. All previous invitations got delivered in no time and all together.

Another bug i'm facing is that the app never finishing install in test flight app, but actually it is installed, just leave the app, and you will find it in the home screen.

Hope it helps someone.

Answer 10

I needed to resend the invitation email to an internal tester. The following work for me:

deselect the invited tester and save. this remove the invite. re-select the same tester and save. this added the tester and re-send the email.

Also, you have to click on the link in the email to see the update. Otherwise, the TestFlight app still shows no app available until you click on the link. I found the email was in the spam folder in the first place ...

Answer 11

• Click on the Internal Testers tab
• Deselect the testers not receiving invites and Save
• Return to the Builds tab
• Click the Invite Testers link that appears
• Reselect the previously deselected testers and Save

Ran into the issue and this worked without a lot of extra / wasted effort

Answer 12

Working with the new Testflight has been pretty frustrating for me as well. After a prolonged phone call to Apple's developer support (1800 633 2152) I finally got to a senior support representative who gave me the following steps and also reassured me that they are aware that this is a workaround and that these issues will be fixed soon. Wish Apple would just own up to their mistakes though and openly apologize to developers etc. This worked for me immediately (all emails got sent out, including ones for previous versions). It also did not require me to delete any users from Users & Roles, which was nice. Shouldn't matter, but I did this in Safari, and after clearing all history, quitting, and re-opening the browser and signing back in.

1. Turn off Testflight Beta testing for the build under that app's "Prerelease" (green toggle switch to the top right of the active build)

2. Deselect the checkboxes for the users in "Internal Testers" and/or external testers, then click save.

3. Go to "Users & Roles" in iTunes Connect, then "TestFlight Beta Testers"

4. Deselect all the users and click save. (For external testers you may need to delete them and re-add them. I didn't have any external testers in my case so I don't know for sure.)

5. Reselect the users and click save

6. Return to the Prerelease section for the app and click "Internal Testers".

7. Reselect the users you want and click save.

8. Back on the Builds page, click to turn TestFlight Beta testing back on for the build you want.

After doing that in that order, I immediately got sent all the missing invites, and also a new user confirmation email that I had tried to send myself.

Note a related problem I had was with users who appeared on both the internal and external list. Try to avoid that because it is buggy.

EDIT: so even though I went through all this, when I tried to use the link in the email I finally got from TestFlight, it said it's invalid!

I did a couple more on/off cycles and I eventually got one that works. Also turning on Testflight testing before selecting the testers may have helped.

Answer 13

This happened to me as well. In the end I just turned off beta testing for the build, re-enabled and re-invited the internal testers, email came through the second time around.

Answer 14

A bit heavy-handed, but it works.

1. Delete the user: Itunes Connect, Users and Roles, Edit, Select user, Delete
2. Re-create the user: (+), name, email, Next, Next, select 'Technical', Save
3. User will get a confirmation email, once they accept,
4. Itunes Connect, Users and Roles, Tap User's email in the list, Enable "Internal Testing"
5. My Apps, Select App, Prerelease, Internal Testers, Select the user, Invite.
6. User will get an email invitation, which they should accept from their device.

You're good to go.

Answer 15

Please do not check/uncheck the Internal Tester status - sending another invite to these guys is a PAIN!

I simply incremented my build from 1.0 to 1.0.1 and submitted the app. The key is - to see if the APP is available right away as 'Active', then great! Else, if its sitting in the 'Processing' section of iTunes Connect (like a Fumb Duck), no use trying to revive that.

So, as soon as you find your app in the Processing Section - wait for about an hour, watch another episode of House of Cards 2.0 (3.0 is boring).. then..

1. Increment Build - add an 0.1 to the current one
2. Validate - dont forget to validate (I validated 3 times, just to be ultra sure)
3. Submit
4. Add Beta Information and Ta Da!

Cheers!

Answer 16

My problem was I had invited everyone from internal testers to external testers as well. Removing them from externals has enabled the internal testing for them.

Answer 17

For new builds on the same version, once the build becomes available, I had to turn OFF testing for that version and immediately turn it back on. This instantly sent an Update notification to TestFlightApp, emailed the testers, and allowed users install the new build.

Answer 18

I have had the same issue. 3 accounts altogether (1 mine, 2 others) initially, mine worked and both of the others. When I tried to update, only one worked. Since the only similarities with the other 2 was that they were GMAIL accounts, so I added one of my apps (to my phone, and I had to log onto test flight using it) - all seems to be working. I was told the Google spam filter was filtering these out and I couldn't figure out how to allow them through.

Answer 19

You have to fill the "What to Test" section. After you will be able to send invites for internal members.

Answer 20

My solution: Use an App Store Distribution profile, not an Ad Hoc Distribution Profile for submitting your app.

And secondly, you have to recreate the App Store Distribution Profile before submitting the app. This will add the betatest entitlement to the profile.

Maybe you need to remove the internal testers from the list and add them again.

Answer 21

I've been round and round on this as well. What finally worked for me was to clear the internal tester status on the user, double check that the account was removed from the Internal / External list and then re-enable tester status for the user. Invite as an internal tester then worked for that user.

Answer 22

This is an outstanding bug. A report has been filed, see details below. To get Apple to address this issue sooner, please submit a similar report through https://bugreport.apple.com