Post

Replies

Boosts

Views

Activity

Reply to TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Still broken here as of today, 7 August 2026 - day 21 for my team. WHAT FAILS POST /v1/betaAppReviewSubmissions returns HTTP 422 with code "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", detail "Beta Contract is missing." The same action in the App Store Connect UI (TestFlight > external group > Builds > +) instead shows "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." My membership is paid through July 2027, so that message is misleading - the UI seems to fall back to a generic renewal prompt when the beta contract lookup fails.WHAT I HAVE RULED OUT Agreements: Paid and Free Apps both Active, tax and banking complete, PLA accepted, nothing pending. Developer Support verified all of it independently. Rebuilding and re-uploading: three separate rounds of fresh builds, no change. Per-app misconfiguration: I created a brand new app after the fault began and it failed on its very first beta submission. Client: reproduces from plain curl, no browser or web session involved. Everything else on the account works normally - uploads, signing, processing, metadata, beta groups and testers, and internal TestFlight distribution. Only the external beta submission call is refused. FURTHER SYMPTOMS Builds that Beta App Review already APPROVED can no longer be installed. One of mine still reports processingState VALID, expired false, BETA_APPROVED, betaReviewState APPROVED - but Install in the TestFlight app returns "The requested app is not available or doesn't exist." Same for every app of mine visible in TestFlight. So this is not only a submission block. Build expiration dates were rewritten in bulk. Every build I uploaded before the break now shows an expirationDate of exactly 17 July 2026 or 31 July 2026 instead of upload + 90 days - two discrete server-side events, one on the day the fault began and one on the day Developer Support looked at my case. Builds uploaded after 1 August show normal 90-day dates again. Both of those look like something operating on the contract record itself rather than on individual submissions. STATUS Developer Support case 102944956353, open since 17 July. I have been asked twice to "upload a new build and wait 48 hours"; both rounds reproduced the error exactly. Filed as Feedback FB24199652 with API traces and the Apple error IDs.
2w
Reply to TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
Still broken here as of today, 7 August 2026 - day 21 for my team. WHAT FAILS POST /v1/betaAppReviewSubmissions returns HTTP 422 with code "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", detail "Beta Contract is missing." The same action in the App Store Connect UI (TestFlight > external group > Builds > +) instead shows "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." My membership is paid through July 2027, so that message is misleading - the UI seems to fall back to a generic renewal prompt when the beta contract lookup fails.WHAT I HAVE RULED OUT Agreements: Paid and Free Apps both Active, tax and banking complete, PLA accepted, nothing pending. Developer Support verified all of it independently. Rebuilding and re-uploading: three separate rounds of fresh builds, no change. Per-app misconfiguration: I created a brand new app after the fault began and it failed on its very first beta submission. Client: reproduces from plain curl, no browser or web session involved. Everything else on the account works normally - uploads, signing, processing, metadata, beta groups and testers, and internal TestFlight distribution. Only the external beta submission call is refused. FURTHER SYMPTOMS Builds that Beta App Review already APPROVED can no longer be installed. One of mine still reports processingState VALID, expired false, BETA_APPROVED, betaReviewState APPROVED - but Install in the TestFlight app returns "The requested app is not available or doesn't exist." Same for every app of mine visible in TestFlight. So this is not only a submission block. Build expiration dates were rewritten in bulk. Every build I uploaded before the break now shows an expirationDate of exactly 17 July 2026 or 31 July 2026 instead of upload + 90 days - two discrete server-side events, one on the day the fault began and one on the day Developer Support looked at my case. Builds uploaded after 1 August show normal 90-day dates again. Both of those look like something operating on the contract record itself rather than on individual submissions. STATUS Developer Support case 102944956353, open since 17 July. I have been asked twice to "upload a new build and wait 48 hours"; both rounds reproduced the error exactly. Filed as Feedback FB24199652 with API traces and the Apple error IDs.
Replies
Boosts
Views
Activity
2w