@DTS Engineer — adding a measured report to this thread. Team W6KJ2VH5S5. Same two symptoms as everyone above, but with one detail I have not seen reported yet, and which should be traceable on Apple's side.
WHAT MAKES THIS ONE DIFFERENT
On 2026-07-15, between 06:35:13 and 06:35:19 Pacific, 400 builds across 15 of our apps were expired in a single batch. That is roughly 57 builds per second over a 7-second window. None of them were near their 90-day lifetime; they were 5 to 33 days old. We issued no such request: our tooling has no code path that expires builds, and it runs no concurrency, so it could not have produced that rate even if it tried. This looks like a single backend write, and it is the exact moment our TestFlight distribution stopped working.
THIS IS A REGRESSION, NOT A NEVER-WORKED ACCOUNT
We have 77 beta review submission records on this team between 2026-02-19 and 2026-06-29T00:38:49Z, 76 of them APPROVED. External beta review worked here for four months and then stopped.
APPLE'S OWN COUNTERS SHOW THE SAME BREAK
Summing betaTesterUsages across all 17 apps: 456 tester sessions in the 60 days ending 2026-07-04, then 6 sessions in the following 23 days.
APPLE'S OWN SYSTEM STILL REPORTS EVERYTHING AS FINE
Builds still reach processingState VALID, and TestFlight still emails us "X is now available to test" (most recently 2026-08-03T08:17:58Z) for builds that cannot be installed. developer.apple.com/system-status currently shows "App Store Connect - TestFlight: available". From the developer side there is no signal at all that distribution is dead.
CURRENT STATE
POST /v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING for every app on the team.
Internal testers get "The requested app is not available or doesn't exist".
All agreements Active, membership active, certificates and provisioning profiles valid.
As heypain noted earlier in this thread, GET /v1/apps/{id}/betaLicenseAgreement returns 200, so the per-app agreement is intact. The missing record is team-level, and the public API has no endpoint that creates it.
THE ASK
In February 2026 you resolved exactly this condition for the original poster on this thread. We are asking for the same backend action for team W6KJ2VH5S5, and, if possible, for the 2026-07-15 batch expiration to be traced, since it may be the cause rather than a side effect.
Existing references: Developer Program Support case 20000125900795 (submitted 2026-08-01, no response yet), Feedback FB24086101, FB24111129 and FB24133326.
