问题

I distributed the first build version of my app to internal testers with iTunes Connect and successfully installed on internal tester's devices. Now, I've uploaded the second build via iTunes Connect. My internal testers have received the email that build 2 is available and clicked on the button to view it in TestFlight, but when TestFlight opens only build 1 shows available to install.

Is there something else that I need to do to make build 2 available to testers, or does it just take some time for it to show up in TestFlight even after the testers get the email that it's available?

回答1:

I've found that sometimes I've needed to toggle the 'TestFlight Beta Testing' switch to get everything to work.

UPDATE: iTunesConnect has been updated since the above answer. Now to reset it you should do the following steps:

Select the 'Not Available for Testing' then tap save.

Hit the 'Select Version to Test' on the right hand side. Select the version you want to test and then hit 'OK'.
Finally hit save and then tap the 'Start Testing' button.

Now you should be good to go!

2018 UPDATE

Itunes connect seems to have changed again. The method above is no longer available. One solution us to expire the build, re-upload, and start testing again. To expire a build, select the build being tested (in the test flight section) the click expire in the top right corner. It should look something like this:

This seems to remove the build from TestFlight and you will need to upload a new build. Not optimal, but I can't find another method right now.

回答2:

Check also if you compiled the app with the right certificate. I got the same issue when uploading a binary compiled with the wrong one (Ad Hoc instead of App Store). App Loader and iTunes didn't complain, but the binary wasn't visible for selection in TestFlight.

回答3:

I had the same problem and the toggle answer didn't work. I had to remove myself as an internal tester and then invite myself agin. After entering the redeem code into the TestFlight App it worked like a charm!

回答4:

I encountered the same issue and I went to the iTunesConnect website -> My Apps -> Selected my app -> Opened the TestFlight tab -> clicked on the build number.

After that, in a few seconds the app showed up in the TestFlight app.

Hope it helps.

回答5:

I tried everything and non worked, for me the following worked:

TestFlight > App Store Connect Users > Testers Tab

I removed the people in the list and added them again. an email was for the first time sent to them including the "view in testflight" button which is what we want!

before this I had filled out the required forms and questions asked by apple in order to run testflihght.

回答6:

I had the same issue. Once I complete the Export Compliance certificate I was able to see the app in TestFlight. There is a high chance that your app may also need to complete it.

In iTunes Connect, go to TestFlight (Tab) > iOS (Sidemenu) > iOS Builds select the latest build and complete the Export Compliance.

On iPhone / iPad - open the TestFlight app > Select your app > Tap into Previous builds - you will be able to see all builds and choose whichever you want to test.

Happy Testing!

回答7:

It is because of your build version is lower than one of your previous builds. You can re-upload highest version of your older builds or you can download before waiting from the mobile app (test flight app) with following steps:

go to test flight mobile app.
click on your latest/current app (it will show you the details of the app).
click on the "Previous Builds".
install your version from here.

回答8:

14-08-2018

This is my workflow

iTunesConnect website -> My Apps -> Selected my app -> Opened the TestFlight tab -> clicked on the build number -> Test Details --> Fill what to Test box --> Save

回答9:

If your latest build still doesn't show on Test Flight, open your email that has received an invitation for testing. Usually, you will receive an invitation from TestFlight.

This email contains an open TestFlight link. I recommend that you login your email on your Mail app. This will automatically open TestFlight and display the latest build.

回答10:

I get this problem al the time as well and for us it is enough to click on the TestFlight tab in itunes connect and the build always appears immediately in TestFlight with a notification

回答11:

I was able to fix this issue by adding the beta-reports-active entitlement. As soon as I added this the next build showed up for in itunes connect.

< key >beta-reports-active< /key >

< false/ >

回答12:

If anyone is still having the issue where the new update is not going out to your testers, what I did was click on the update I wanted to send out and next to the button that says Expire build I clicked notify testers that refreshed their TestFlight and sent out the new update.

回答13:

This also occurs if you click on the TestFlight tab BEFORE your current version has had a BUILD selected.

回答14:

In my case, reloaded the page and found latest version was shown.

回答15:

In my case,

It didn't show in TestFlight build until I incremented the app version from 1.0 to 1.1

So try incrementing current version and build.

回答16:

Remove tester from tester list in itunes and add again. Refresh test flight app on mobile and then you can see the new update.

回答17:

I had the same issue and I only had to log out from App Store Connect Web application and then log in again. When then went to TestFlight tab the build was there.

回答18:

This workflow was the unique that works for me.