Post

Replies

Boosts

Views

Activity

TestFlight Beta App Review Submission Fails with HTTP 422 — BETA_CONTRACT_MISSING (Unresolved for Over a Month)
Hi everyone, I've been struggling with a TestFlight issue for over a month, and I'm hoping someone here has encountered something similar or knows how to resolve it. I'm developing an iOS app called Bondi, and every time I try to submit a new build for external beta testing, App Store Connect returns an HTTP 422 error. I've tried contacting Apple Developer Support, but I haven't received a helpful response, and I'm completely blocked from distributing new builds to my external testers. The error: When submitting a build for Beta App Review, the following API request fails: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "9fc5c303-4edb-4aee-9b39-75c8c8c53e1c" } } } } } The browser console shows: The server responded with a status of 422. API Response Error: TF_BETA_APP_REVIEW_RESPONSE status code: 422 api correlation key: SRKTSBKDZ2F7XPBJH7XFYSBUL4 In previous attempts, I also encountered this error: `ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING im not sure it's connect but I also noticed the following console warning: fetched via init(), using default/cached config values. What I'm trying to understand Has anyone encountered BETA_CONTRACT_MISSING when submitting a TestFlight build? Does TestFlight require any additional agreements, even for completely free applications? Could this indicate an issue with my Apple Developer account rather than the app itself? Is there any workaround to reset or reinitialize the TestFlight beta agreement? Can someone from Apple confirm whether this is a known issue? I've been blocked for over a month, and it's incredibly frustrating that App Store Connect provides no meaningful explanation of what's wrong.
1
0
34
13h
TestFlight Beta App Review Submission Fails with HTTP 422 — BETA_CONTRACT_MISSING (Unresolved for Over a Month)
Hi everyone, I've been struggling with a TestFlight issue for over a month, and I'm hoping someone here has encountered something similar or knows how to resolve it. I'm developing an iOS app called Bondi, and every time I try to submit a new build for external beta testing, App Store Connect returns an HTTP 422 error. I've tried contacting Apple Developer Support, but I haven't received a helpful response, and I'm completely blocked from distributing new builds to my external testers. The error: When submitting a build for Beta App Review, the following API request fails: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "9fc5c303-4edb-4aee-9b39-75c8c8c53e1c" } } } } } The browser console shows: The server responded with a status of 422. API Response Error: TF_BETA_APP_REVIEW_RESPONSE status code: 422 api correlation key: SRKTSBKDZ2F7XPBJH7XFYSBUL4 In previous attempts, I also encountered this error: `ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING im not sure it's connect but I also noticed the following console warning: fetched via init(), using default/cached config values. What I'm trying to understand Has anyone encountered BETA_CONTRACT_MISSING when submitting a TestFlight build? Does TestFlight require any additional agreements, even for completely free applications? Could this indicate an issue with my Apple Developer account rather than the app itself? Is there any workaround to reset or reinitialize the TestFlight beta agreement? Can someone from Apple confirm whether this is a known issue? I've been blocked for over a month, and it's incredibly frustrating that App Store Connect provides no meaningful explanation of what's wrong.
Replies
1
Boosts
0
Views
34
Activity
13h