We are unable to submit a valid build for external TestFlight beta review because App Store Connect reports that the beta contract is missing for the app. App: Nagram App Apple ID: 6781000861 Bundle ID: xyz.nextalone.nagram Version / build: 12.8 (33174) Build ID: ac9516ad-b435-4d2f-ae3f-2d8abaec023d The UI path is App Store Connect > Nagram > TestFlight > External group > Builds > Submit for Review. The UI shows: There was an error processing your request. Please try again later. The underlying POST to /iris/v1/betaAppReviewSubmissions returns: HTTP 422 code: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING title: Beta contract is missing for the app. detail: Beta Contract is missing. error id: 89b6d5d0-194d-4467-a75c-741aa285e1b7 I checked the surrounding state: The build is VALID, expired=false, and externalBuildState=READY_FOR_BETA_SUBMISSION. Beta App Review information exists. Beta app localization exists. Build What to Test exists. Beta license agreement exists. Account-level Free Apps and Paid Apps agreements show Active / InEffect. Bank, tax, DSA, and account compliance entries show Active. The current user has Admin / Legal / CIPS roles and current ASC terms are signed. This same external TestFlight group previously had approved builds, so external testing worked before. I also opened Developer Support cases, but this looks like an Apple-side missing or detached TestFlight beta contract state for this app/account. Recent support case IDs: 102919547161 and 102919547336. Has anyone seen this state repaired without creating a new app record? Is there any App Store Connect action that can re-provision the beta contract state, or does Apple need to repair it server-side?We are unable to submit a valid build for external TestFlight beta review because App Store Connect reports that the beta contract is missing for the app. App: Nagram App Apple ID: 6781000861 Bundle ID: xyz.nextalone.nagram Version / build: 12.8 (33174) Build ID: ac9516ad-b435-4d2f-ae3f-2d8abaec023d The UI path is App Store Connect > Nagram > TestFlight > External group > Builds > Submit for Review. The UI shows: There was an error processing your request. Please try again later. The underlying POST to /iris/v1/betaAppReviewSubmissions returns: HTTP 422 code: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING title: Beta contract is missing for the app. detail: Beta Contract is missing. error id: 89b6d5d0-194d-4467-a75c-741aa285e1b7 I checked the surrounding state: The build is VALID, expired=false, and externalBuildState=READY_FOR_BETA_SUBMISSION. Beta App Review information exists. Beta app localization exists. Build What to Test exists. Beta license agreement exists. Account-level Free Apps and Paid Apps agreements show Active / InEffect. Bank, tax, DSA, and account compliance entries show Active. The current user has Admin / Legal / CIPS roles and current ASC terms are signed. This same external TestFlight group previously had approved builds, so external testing worked before. I also opened Developer Support cases, but this looks like an Apple-side missing or detached TestFlight beta contract state for this app/account. Recent support case IDs: 102919547161 and 102919547336. Has anyone seen this state repaired without creating a new app record? Is there any App Store Connect action that can re-provision the beta contract state, or does Apple need to repair it server-side?

All TestFlight builds for my app expired at the same time, overnight, with no action on my side. New builds upload fine and show “Ready to Submit,” but: Internal testers (and I) cannot install: “The requested app is not available or doesn’t exist.” -Submitting for external review fails with 422: PARAMETER_ERROR.REQUIRED / filter[build]. Internal testing worked perfectly before and broke overnight. This appears to be a known recurring backend issue. All agreements, banking, tax, and export compliance are Active. DSA declaration is currently In Review. I’ve opened a support case (aprox. 5 days ago, only automated reply so far). Has anyone resolved this, or can a DTS engineer help escalate? Bundle ID available on request.

Hello, I created an app using the latest version of Xcode (16.2), and I'm having a problem testing this app on my iPhones. I created this app just like all the others I've made for my clients, including one on (03/24/25), but when I went to upload another App to App Store Connect on (03/26/25) I couldn't test it on my phone. Points to consider: The app runs perfectly on the Emulator. All my terms and agreements with Apple are up to date. I tried to download the apps through Testflight on 2 different devices, iPhone 7 Plus (iOS 15.8.1) and iPhone 15 Pro Max (iOS 18.3.2), and I was unsuccessful in neither attempt. I can send my app to the internal testers, but when I click download, the following message appears: Could not install [APP NAME]. The requested App is not available or doesn't exist. I imagine this problem is with Apple itself, I have already contacted support, but I need to resolve this urgently for my customers. Has anyone experienced this and resolved it?

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

my app build is stuck on preprocessing build from one hour

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

So I am adding Catalyst support to my iOS app. I went through and updated my code and Build Settings to add Catalyst support. I can build for any iOS build or macOS build. I went into App Store Connect and then added a macOS build. I am not able to do a single build and archive that uploads a build for both macOS and iOS. I can do a build and archive for "Any iOS Device (arm64)" and it shows up in the iOS test flight. I can do a build and archive for "Any Mac (Mac Catalyst, arm64, x86_64) and it shows in the macOS test flight. Maybe I'm making a bad assumption ( I could not find any documentation on it) but I assumed Catalyst was a single build and archive that showed up in BOTH macOS and iOS sections. The build settings seem to imply the build is good for a single build and archive process. I want this to be a universal app and my assumption doing it that way would keep everything in sync when you push to the App Store. You can already download the app through the App Store but it is a version of the iPad app. I was hoping to make it more native and available in the Mac App Store without the iPhone/iPad app option. Am I making bad assumptions? Will I just have to do two Build and Archives for every build? I just want to make sure I'm doing this correctly and the best way.

We are experiencing an issue with our iOS application (MotoDealz) distributed through TestFlight. App Details: App Name: MotoDealz Version: 1.4.36 Builds: 48 and 49 Issue: The application installs successfully through TestFlight, but when launched on a physical iOS device it displays only a blank white screen and does not proceed further. Observations: The same build works correctly in the iOS Simulator. Build processing completed successfully in App Store Connect. No crash dialog or error message is displayed. The issue is consistently reproducible after reinstalling the TestFlight build. The application remains on a white screen indefinitely. Environment: Distribution Method: TestFlight Physical Device: iPhone Simulator: Working as expected Has anyone encountered a similar issue where the app works correctly in the simulator but shows only a white screen in TestFlight builds on physical devices? Any guidance regarding diagnostics, device logs, release-build configuration, or TestFlight-specific troubleshooting would be greatly appreciated. Thank you.

Hi everyone, I am currently completely blocked from submitting my new app for TestFlight Beta Review (External Testing). The App Store Connect web interface fails to submit, and when I try to bypass the UI using the App Store Connect REST API to create a betaAppReviewSubmissions request, Apple's servers return the following 422 error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Here is what I have already checked and verified on my end: Agreements, Tax, and Banking: My "Paid Apps Agreement", "Free Apps Agreement", "U.S. Tax Forms", and "Bank Accounts" all clearly show as "Active" status. There are absolutely no pending banners or unaccepted agreements on developer.apple.com or appstoreconnect.apple.com. Apple Developer App: I logged into the official iOS Apple Developer app with the Account Holder ID, and there are no hidden agreements to accept there either. App Privacy: All data collection questions are answered, and the App Privacy section is fully Published. Test Information: All required Beta App Review details (Name, Email, Phone) are correctly filled. Export Compliance: My Info.plist includes <key>ITSAppUsesNonExemptEncryption</key><false/>, and the build attributes confirm it. It appears that my TestFlight beta contract has somehow become detached, bugged, or failed to provision on Apple's backend. Has anyone experienced this specific API error recently? Is there a way to force the system to re-provision the contract, or does this strictly require manual intervention from an Apple Engineer? Any guidance would be highly appreciated. Thanks!

Hi there, this is my first app, so please be gentle. I submitted it on 6/16 (3 days ago) and I saw somewhere that it took 24-48 hours to be reviewed, and I believe that's when the people I invited to test it would start getting their email invitations. It's still at "Waiting for Review" on the Test Flight tab. Is this the same as THE "app review"? Or is it some "mini-review" for Test Flight? Either way, when should I start following up?

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Nagram app 6781000861 / xyz.nextalone.nagram cannot submit build 12.8 (33174), build id ac9516ad-b435-4d2f-ae3f-2d8abaec023d, for external TestFlight review. App Store Connect UI says there was an error processing the request. The betaAppReviewSubmissions POST returns HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, detail Beta Contract is missing, error id 89b6d5d0-194d-4467-a75c-741aa285e1b7. The build is VALID and READY_FOR_BETA_SUBMISSION, and beta review info, beta localization, What to Test, beta license agreement, and Free/Paid Apps agreements are active/in effect. Support cases: 102919547161 and 102919547336. Is this repairable in App Store Connect, or does Apple need to repair the beta contract state server-side?

TestFlight sends automatic e-mail notifications to beta testers, with the subject "AppName 1.2.3 (123) for iOS is now available to test." etc. At the bottom of these messages is an "Unsubscribe" link, which is a mailto: link that sends an e-mail to the app's support contact address with of the form mailto:developer?subject=Unsubscribe from TestFlight&body=tester wants to stop receiving TestFlight emails about AppName Unfortunately, app developers cannot manage an individual testers' notification settings. This creates a frustrating support loop where the developer has to reply directing the tester to disable e-mail notifications for themselves within the TestFlight app. Am I missing something? (Also reported to Apple as FB19806347)

Hi Have uploaded the build version and status now is approved, but this build is not showing under testflight previous builds, not able to install this version. Also when adding independent tester, error occured showing like bolow, retry not work. Anyone facing this problem ?

A few days ago I uploaded a build to Testflight successfully. Just now I made absolutely no changes whatsoever other than to increment the build number. This latest build doesn't appear in Testflight. Tell me this can't be anything other than a bug with Testflight, if a build from a few days was good enough to appear, then how come with no changes it no longer is.

My app was submitted to the appstore connect via transport. The logs show no errors, the status has been “The App is Processing“ for over a week. I opened a ticket, nobody responded. I called, spoke to support. They could not identify the issue, and escalated. It’s now beed several days and I have had no response. In appstore connect Testflight It shows no build processing.

Hi everyone, App Name: StAIle Build: 6 (Version 1.0.0) I submitted this build for TestFlight external testing on June 12, 2026. It has been stuck in "Waiting for Review" status ever since (6+ days now), well beyond the typical 24-48 hour window. What I've tried so far: Sent an email to App Store Connect support — no response after 2+ days Submitted an expedited review request via the official form — still waiting on that too No message in the Resolution Center, no compliance flag I'm a solo developer trying to run external beta tests before submitting the app for full App Store review, and this delay is blocking that step entirely. Has anyone else experienced something similar recently, or found a way to get this moving? Any advice appreciated. Thanks!

Hello, I am experiencing the exact same ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING issue. I cannot submit builds for External TestFlight review. When I click "Submit for Review" in TestFlight, App Store Connect returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING "Beta contract is missing for the app." All agreements, banking information, and tax forms are Active. Completed and verified: • Paid Apps Agreement = Active • Free Apps Agreement = Active • Bank Account = Active • W-8BEN Tax Forms = Active • Compliance information completed • Account Holder role assigned correctly I have already: • Added and activated a bank account • Completed all tax forms • Uploaded new builds after activation • Waited several days for synchronization • Opened a case with Apple Developer Support Developer Support has already escalated my case to the senior team, but the issue remains unresolved. The browser console confirms: 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING This issue is currently blocking External TestFlight testing. Has anyone experienced this recently? Could someone from Apple verify whether the TestFlight Beta Contract associated with the account needs to be reset, recreated, or manually refreshed? Thank you.

Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?