Post not yet marked as solved
Click to stop watching this thread.
You have stopped watching this post. Click to start watching again.
contentPostList.repliesup-voted.tooltip
I had a similar problem where a new build would show in the Apple Developer Portal as "Ready to Test" but would not show up for Internal Testers in the TestFlight app. For me the solution was to "expire" all previous builds. Once I did that the new build immediately showed up in TestFlight.
Normally I don't do this and I typically have many builds "available" so I was wondering why I had to expire all builds this time. What was different...
Before this build my Apple Distribution Certificate had expired so I did have to make a new one before the upload process would complete. So my suspicion is that TestFlight will not show builds for the same bundleID signed with different certificates. That would explain why expiring old builds solved the problem.