422 - Beta Contract Missing

Question

Created 3w

Replies 5

Boosts 2

Views 1k

Participants 3

Hi,

I'm a new Apple Developer program member and over about a 10-day period, I have been blocked from beta testing my app. I have been getting repeated 422's about a TestFlight Beta contract not attached to app 6812131455 . I submitted a Feedback Assistant ticket, FB24795679, where an engineer replied and said things were unblocked. I believe that I was able to get one more build uploaded after that but then the problem recurred and completely blocked me from sharing the TestFlight External beta link with new testers.

I am uploading using the Transporter App and then trying to attach in Appstore Connect. I emailed Apple Developer support and they sent me only basic information about what 4xx HTTP status codes were, so I followed up via phone to Developer Support under ticket 102964195981. I've been calling over the past 3 days and a Senior Advisor has not picked up the ticket yet.

Diagnostic information is below, including a sanitized HAR file. The error is reproducible, even with new builds, even with going through and confirming all requested data input fields are filled out and agreements are signed (to the best of my knowledge).

I am developing an ad-free, free app with a focus on accessibility for the visually impaired. Can someone help me find a durable solution here?

Much appreciated--I see others have had this issue. Happy to capture further debug logs to assist in a fix.

captured_at_utcsourcebuild_numbermethodurlhttp_statuserror_codeerror_idx-apple-jingle-correlation-keyx-apple-request-uuidx-responding-instance

2026-09-24T15:07:48.547415+00:00

live

116

POST

/iris/v1/betaAppReviewSubmissions

422

ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING

7ef85ee6-412e-4535-b8f7-16cb8da406c8

5QSUAQZ4MOELPIGMJXUJD4UBP4

ec254043-3c63-88b7-a0cc-4de891f2817f

ac-gateway-api:ac-gateway-api-main-5d674cb558-bp79n:ac-gateway-api-main-5d674cb558-bp79n👎 :::prod

failures-422.md

failures.jsonl

failures.md

session.sanitized.har

Answer 1

mertozdemir OP

3w

Same issue here, on multiple apps under our team.

Feedback Assistant: FB24923952 Developer Support case: 102970576491 (open 5 days, no response) Team ID: DBD8C84SD6 Affected App IDs: 6813978702, 6808238004, 6813906917

POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING (request ID: 13ac59e5-6047-4581-aefe-83ea336a5a2b)
Builds are processed and valid: internalBuildState = IN_BETA_TESTING, externalBuildState = READY_FOR_BETA_SUBMISSION
Internal TestFlight builds are listed but cannot be installed by any tester, on any device or Apple ID
Free Apps and Paid Apps Agreements, bank account and tax forms are all Active; Test Information is complete
The same behavior occurs on other independent teams at the same time

This is blocking a client delivery. If someone from Apple could route FB24923952 to the TestFlight team to check the beta-contract state for our team, it would be greatly appreciated.

Thank you.

Answer 2

helpYourNeighbor OP

1w

A Senior Advisor from developer support replied, reset things, asked me to try again in 48 hours, and I was able to upload another build.

However, the problem has again recurred, with my build #124.

Answer 3

iamjono OP

1w

OP, you are lucky. I've had zero response.

Answer 4

helpYourNeighbor OP

1w

The second time this recurred, I uploaded a build at 8:30 PM at night. At 1:30 in the morning, I received an email that it was ready to test. Great! When I went into my account, though, the build (123) and all other builds were marked expired. When I uploaded 124, it processed OK but then threw the beta contract error when I tried to attach it to the beta.

My developer imagination here is wondering if there was a false positive on some security scan somewhere. As in, I sent him an email at 1:30 AM but he didn't act on it. People are sleeping! Abort! Better to have a human being review things than to take a chance on having an app go out to even a test group while people are sleeping.

I'm very glad that layers of security are in place for our users. I just wish someone would tell me what the secret sauce is. Upload a build in the morning, wait 5 hours, install a test build immediately upon approval, what?

The 422 is just so opaque, I can't iterate like this and it's holding my project back.

Answer 5

iamjono OP

1w

Agreed. This has stopped 3 apps from going into active testing on iOS now. They're getting dangerously out of sync with their Android counterparts. Apple, please get this sorted, it's a mess!