I’m experiencing what appears to be a team/account-level TestFlight backend issue, and it is currently blocking my development workflow. Team ID: TJ6F83PA4W What happened All existing TestFlight builds across my apps suddenly became Expired / unavailable. This happened across the developer team rather than to one particular app or build. I then uploaded a completely new build to determine whether the previous builds had simply been reset or invalidated. Test app: RESON | See the frequency. Apple ID: 6799940431 Version: 1.0.0 Build: 2 The new build: Uploaded successfully Processed successfully Appears normally in TestFlight Shows a fresh 90-day testing period Has an active Install button But installation immediately fails with: Could not install RESON | See the frequency. The requested app is not available or doesn’t exist. So this does not appear to be normal build expiration. A completely new and successfully processed build is also affected. Troubleshooting / support I have already opened an Apple Developer Support case: Case ID: 20000133520102 I’ve contacted Developer Support multiple times by email and also requested/spoken through phone support, but the issue remains unresolved and is now blocking my TestFlight workflow. I have intentionally not started changing certificates, provisioning profiles, Bundle IDs, or repeatedly uploading replacement builds because the symptoms affect the entire team and appear to occur at the TestFlight distribution stage. I’ve also seen reports from other developers describing similar symptoms, including references to BETA_CONTRACT_MISSING / missing Beta Contract backend state. I cannot confirm that this is the cause on my account, but the symptoms appear similar. Question for Apple / other developers Has anyone experienced this exact combination? All TestFlight builds unexpectedly expire → new builds process successfully → builds appear available for 90 days → installation fails with “The requested app is not available or doesn’t exist.” If someone from App Store Connect / TestFlight engineering sees this, could you please advise whether the Beta Contract / TestFlight distribution provisioning state for the Developer Team needs to be checked or re-provisioned server-side? Any confirmed workaround or escalation path would be greatly appreciated.