BETA_CONTRACT_MISSING + "The requested app is not available or doesn't exist" on all apps — agreements Active, support case open, same backend issue?

Hoping a DTS engineer can take a look, as this seems to be the same backend issue described in threads 814565, 815875, 815885 and 813703.

What's happening (team N74PHKXB5Q, individual Account Holder):

  • Every TestFlight build on the account expired at the same moment on 30 Sep 2026, across unrelated apps.
  • New builds upload and process fine (1.0 (2), (3), (4) of app 6817732435 are all Complete / In Beta Testing), but tapping Install in TestFlight on iPad and iPhone fails instantly with "Could not install - The requested app is not available or doesn't exist". The device log shows the install request to testflight.apple.com/v2/accounts/.../builds/.../install returning HTTP 404 (X-Apple-Jingle-Correlation-Key KARDZQVMLS5G3EAMOGBKFYGFEE).
  • Submitting the same build for external testing through the App Store Connect API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING "Beta contract is missing for the app".
  • "Report a Problem" from inside TestFlight opens a page that says it can't be found.
  • Paid Apps and Free Apps agreements, bank and tax forms are all Active with nothing pending; the tester (the Account Holder) is Internal / Accepted; app availability is all territories; devices restarted; VPN off; testers removed and re-added with a fresh invite. App Store downloads work normally, so it's TestFlight only.

Developer Support case 102981727998 was opened on 1 Oct 2026 with all of the above. No reply yet.

Two questions, asked genuinely rather than as a complaint:

  1. Is this the known "Beta Contract entity not re-provisioned" condition from the threads above, and can it be re-provisioned on this account? I have a family member waiting to test a build for a wedding in November, so I'd be very grateful for a nudge.

  2. For future reference, what actually triggers it (membership renewal? agreement regeneration?) and is there anything a developer can do on their side to avoid or clear it, rather than waiting on a support case? Several of us seem to hit the same wall and the only documented fix so far is an engineer doing it manually.

Happy to provide the full device log or file a Feedback Assistant report if that helps. Thanks for reading.

BETA_CONTRACT_MISSING + "The requested app is not available or doesn't exist" on all apps — agreements Active, support case open, same backend issue?
 
 
Q