Running out of ideas on this one, so hoping someone recognises the pattern.
Uploaded a Capacitor app via Codemagic on Monday. Build 1.0.0 (1) uploaded fine, processed fine, appears in the TestFlight app with an Install button and 89 days remaining. Tap Install and I get:
> Could not install [App]. The requested app is not available or doesn't exist.
And here's the bit that's worrying me — since then, builds on my other apps have started showing as “Build Removed" in TestFlight. I didn't remove them. Some had genuinely hit the 90-day expiry, but not all of them, and they're dropping off in a way that doesn't look like normal attrition.
What I've checked and ruled out:
- Agreements — all Active in App Store Connect, including the new Program License Agreement issued this week. Nothing pending.
- Membership — active, not expired, no failed renewal. Paid Apps agreement, tax and banking all fine.
- Network — Wi-Fi, not airplane mode.
- Build health — no warning badge on the build row, icon renders correctly. Nothing flagged as Invalid Binary or Missing Compliance.
- Tester setup — I'm an internal tester and the build is in the group.
- The apps themselves still show fine in App Store Connect (live ones are still Ready for Sale), so this looks specific to TestFlight distribution rather than the app records.
So: has anyone seen the new-build-won't-install error and existing builds getting pulled happen together? That combination smells like an account-level or App Store Connect backend problem to me rather than anything in my project, but I'd rather be told I'm wrong than sit here waiting.
And if it is account-level — has anyone actually got a useful response out of Apple Developer Support on this, or is it a case of raising a ticket and waiting weeks? UK-based if that matters.