A brand new app, uploaded through the normal export and upload flow, processes fine and shows "Ready to Submit" in App Store Connect. An internal tester sees it under "Currently Testing" in TestFlight, but tapping Install immediately shows: Could not install RollWave. "The requested app is not available or doesn't exist." This happens for all six builds I have uploaded. The Installs column in App Store Connect stays empty. The same source installs and runs from Xcode. Environment Device: iPhone XS Max, iOS 18.7.10 (registered in the developer account) Build tools: Xcode with the iOS 27.1 SDK, deployment target iOS 17.0, Swift 5.10, arm64 only Dependencies via Swift Package Manager: Google Mobile Ads 13.11.0, which pulls in Google User Messaging Platform 3.1.0 Tester: one internal tester in one internal group. Invitation accepted. The TestFlight app on the device shows the right build number. Account: new developer account. Free Apps Agreement became active on Oct 14, 2026. Paid Apps Agreement is Pending User Info because no bank or tax details are entered (the app is free). TestFlight app version on the device: [fill in] What I checked and changed, in order Minimum OS. Build Metadata shows minimum iOS 17.0 and Required Capabilities arm64. The phone is on iOS 18.7.10, so this is not an OS mismatch. Thinning variants. The "App File Sizes" table in Build Metadata lists an "iPhone XS Max" row (2.26 MB download), so a variant exists for the device. Price and availability. The app had no price schedule and no availability set when I first tried. I set Free and all countries and regions. Failure unchanged on later builds. Agreements. Free Apps Agreement is Active. Digital Services Act status is Active. Beta App Information. It was empty. I filled in the description, feedback email and privacy policy URL. No change. Device family. My project set iPhone only, but the target-level setting overrode it, so the build was flagged "iPhone, iPad". I fixed the target setting. No change for TestFlight. Privacy manifest. After submitting build 4 for review, App Review returned Invalid Binary with ITMS-91064 (invalid tracking information in the app's own PrivacyInfo.xcprivacy). Upload-time validation had passed. The manifest had NSPrivacyTracking true and an empty NSPrivacyTrackingDomains array. Removing the empty array key fixed the rejection. TestFlight install did not change on later builds. Upload path. Builds 1 to 5 were uploaded with altool and an API key after xcodebuild -exportArchive. Build 6 was exported and uploaded through xcodebuild -exportArchive with destination = upload (the same engine as Organizer). Same failure. Client side. Reinstalling TestFlight, restarting the device, and uploading fresh builds changed nothing. [Add anything else you tried.] Install from Xcode. [Fill in the result of running the app on the iPhone from Xcode.] One odd thing I found Both Google SDKs are static binary frameworks that Xcode embeds as small stub frameworks (only a privacy manifest and an empty dylib). The stub for User Messaging Platform declares MinimumOSVersion 100.0 in its Info.plist and minos 100.0 in its Mach-O build load command. Every release I downloaded, 2.7.0, 3.0.0 and 3.1.0, has that same Info.plist value, so it is how Google ships the framework. The stub for Google Mobile Ads says 13.0. I could not confirm whether this affects TestFlight, because I cannot test an install without the stub. It is the only unusual value in the bundle. Related reports Several other threads describe the same alert for internal testers with no confirmed cause or fix, for example thread 812811 and thread 829465. Some say it affects every app on the account or team and that Apple Support fixed it on their side. Questions Has anyone seen this resolved by something other than Apple Support? Can an embedded stub framework with MinimumOSVersion 100.0 break TestFlight installs while upload validation and processing still succeed? Is there any way to see why a build is unavailable to a specific tester, for example a distribution state in the API? I have a support case open or about to be opened and can share app and build identifiers with Apple on request.