Menu
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?
749
Simply go to your app's TestFlight page, click an existing group, and click Enable Public Link. You can then copy the link and share it on social media, messaging platforms, email campaigns, and more.
After uploading a build, iTunes Connect performs some processing to prepare it for TestFlight Distribution and App Store distribution. The status of the build should go to ready after some time. Sometimes, this happens as fast as 15 minutes after uploading but can sometimes take 1 hour or longer.
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:
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!
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.
78
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.
45
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!
9
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.
7
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
