TestFlight external testing blocked: BETA_CONTRACT_MISSING (422) although all agreements are Active

App Store Distribution & Marketing TestFlight
isainal OP
Created
Replies 1
Boosts 0
Views 96
Participants 2

Hello,

Every submission of our builds to external TestFlight testing (Beta App Review) fails with:

422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING

The error is returned by POST /iris/v1/betaAppReviewSubmissions.

Account status as of October 21, 2026:

Free Apps Agreement: Active (Oct 14, 2026 – Jul 13, 2027)
Updated Program License Agreement: accepted
DSA trader status: Active
Builds 2 and 4: VALID, not expired, externalBuildState = READY_FOR_BETA_SUBMISSION
Test Information: all fields filled in

The error first appeared while the updated Program License Agreement was still pending. Accepting it did not resolve the issue.

This looks like the same problem reported in https://developer.apple.com/forums/thread/814565 (also threads 815875, 815885, 821498 and 809728). In that thread the issue was fixed on Apple's side by recreating the team-level beta contract record. As far as we know there is nothing a developer can do from App Store Connect.

Team ID: B7XHH6RU95
Developer Support case: 102996652296
Feedback Assistant: FB25275230

Could someone at Apple please check the beta contract record for our team?

Thank you.

Replies  1
Boosts 0
Views  96
Participants  2
Pokpong OP

Given the active agreements and builds already marked READY_FOR_BETA_SUBMISSION, this does look separate from the usual missing-agreement or build-processing checks. I would keep the existing Developer Support case open and ask them specifically to verify the team-level beta contract record used by betaAppReviewSubmissions. Include the exact UTC time of a fresh failed submission and any request or correlation ID from the response, with the team ID and affected build numbers.

I would avoid repeatedly resubmitting or uploading replacement builds until Support confirms the contract state, since the response points to the account or team record rather than the binary. If you have not already, attach a screenshot of Agreements showing Active and the build details showing READY_FOR_BETA_SUBMISSION to the case. There may not be an App Store Connect setting you can change to clear this error yourself.