I’m having a strange TestFlight issue with one of my builds.
Version 1.0.0 has two builds. Build 1 works normally in TestFlight, but Build 2 is unavailable to every tester I’ve tried.
Build 2 was uploaded successfully, and App Store Connect shows it as “Testing”. I also received Apple’s email saying version 1.0.0 (2) is available to test.
However, Build 2 still can’t be accessed through internal testing, external testing, or a public link.
For internal testing, I assigned only Build 2 to the group, but TestFlight shows “No Builds Available”.
I tried the same with an external testing group and got the same result: “No Builds Available”.
The public link is enabled with no device or OS restrictions, but new testers see “This beta isn’t accepting any new testers right now.”
I’ve already tried removing and re-adding testers, recreating testing groups, removing and re-adding Build 2, disabling and re-enabling the public link, resending invitations, removing the app from the device, stopping testing in TestFlight and joining again, and testing with Build 2 as the only build assigned.
None of that changed the result.
Build 1 still works normally for the same app.
Build 2 details: Version: 1.0.0 Build: 2 Minimum iOS version: 15.0 Device family: iPhone Architecture: arm64
The test device meets the compatibility requirements.
There is also an upload warning: 90737: Missing Document Configuration
The same warning appears on both Build 1 and Build 2, but Build 1 is distributed normally.
Has anyone seen a TestFlight build that shows as “Testing” and generates Apple’s “available to test” email, but still isn’t available to internal testers, external testers, or public-link testers?
Could there be some server-side TestFlight distribution state or App Store Connect setting causing this?
Thanks.
