@DTS Engineer, filed as FB25247970 (area TestFlight). Developer Support cases: 102999662057, 103001563221 and 103001611411. The expiry event. On 16 October 2026 at 06:15:05 PDT, every build uploaded on 15 October was given the same expirationDate, about one day after upload. That was also the first day of our new membership year. The last successful TestFlight install was on 15 October (app 6823172521, build 2026.1015.1343). Fresh uploads don't work around it. New builds get a normal 90-day expiry, process as VALID / Ready for Beta Testing, and still won't install: 6823172521 (com.questapp.mobile): every build. 6824002784 (com.tinyquest.app): a brand-new app record created after the problem started. Build 2026.1019.1141, VALID, in an internal group with access to all builds. 6748294968 (com.gregorylime.somni): a separate, older app record. A fresh build 26, made with Xcode 27 and the iOS 27 SDK, fails the same way. Already ruled out: Membership is active, and all agreements are active and accepted. All apps are "Prepare for Submission". None was ever released or removed from sale. All are available in 175 countries or regions. The tester is the Account Holder, with the same Apple Account in TestFlight and Media & Purchases. Two different iPhones fail the same way. We expired all builds, removed and re-added testers, and uploaded fresh builds. We created a new Apple Distribution certificate and a new App Store profile. Development and Ad Hoc builds of the same apps install and run fine on the same iPhones. Freakster's call above suggests TestFlight access gets revoked at the team level ("it happens sometimes"). That matches what we see: the problem follows the team, not an app, build, certificate or device. Could someone on the TestFlight team check team V294T9786Z? Thank you.