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.

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?

90338: Non-public API usage. The app references non-public symbols in TrustAPP: __ZN3re210chartoruneEPiPKc, __ZN3re210runetocharEPcPKi, __ZN3re211perl_groupsE, __ZN3re212posix_groupsE, __ZN3re214unicode_groupsE, __ZN3re215num_perl_groupsE, __ZN3re216CharClassBuilder11RemoveAboveEi, _ZN3re216CharClassBuilder12AddCharClassEPS0, __ZN3re216CharClassBuilder12GetCharClassEv, __ZN3re216CharClassBuilder6NegateEv, __ZN3re216CharClassBuilder8AddRangeEii, __ZN3re216CharClassBuilder8ContainsEi, __ZN3re216CharClassBuilderC1Ev, __ZN3re216num_posix_groupsE, __ZN3re216unicode_casefoldE, __ZN3re218num_unicode_groupsE, __ZN3re220num_unicode_casefoldE, __ZN3re26Regexp11NumCapturesEv, __ZN3re26Regexp13CompileToProgEx, __ZN3re26Regexp13ComputeSimpleEv, __ZN3re26Regexp15AddRuneToStringEi, __ZN3re26Regexp17ConcatOrAlternateENS_8RegexpOpEPPS0_iNS0_10ParseFlagsEb, __ZN3re26Regexp20CompileToReverseProgEx, __ZN3re26Regexp6DecrefEv, __ZN3re26Regexp6IncrefEv, __ZN3re26RegexpC1ENS_8RegexpOpENS0_10ParseFlagsE, __ZN3re28fullruneEPKci. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. I installed the Didit SDK in the project and now the build doesn't go to TestFlight, as it did above. What could be the problem?

Are there issues with Testflight Beta Review process? My app (minor version update) has been sitting in waiting for review for a over 24 hours where previously it would take a few hours.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. From 8th of June, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch again, there is no any response when tapping the app icon. I managed to export some system logs, and this info in the screenshot looks suspicious. Does anyone have the same issue? Recently the app has been transferred to another developer account, not sure if it is related, this TestFlight version was rebuilt with the new team

Hi, I really need help to resolve the issue with submitting build made with 26.2 for review to release TestFlight build to external testers. I'm always getting "This build is using a beta version of Xcode and can’t be submitted". I tried everything from cleaning DerivedData to fully reinstalling Xcode and tools to 26.2. Even tried earlier Xcode release versions and after pressing Submit for review I always face the same issue. Nothing helps and I can't share my first app with volunteers to test. By Jan 6 2026, my Xcode 26.2 is up to date with App Store and in Xcode Organizer I choose App Store Connect and press Distribute.

Can anyone help me with this error message? Beta contract is missing for the app. Error IDs: 3976de05-9ac1-41e1-9294-a8827535015e 96bfccea-8fe8-450a-8cff-fbc55b696b29 I have tried looking at agreements, there is nothing to sign or that I have not accepted. I cannot find any agreement related to this. I have tried sending my app for TestFlight review from web browser or TestFlight app in my iPhone but no help at all I get the same error message. I have tried sending request to Apple support to call me but that also ends up with error. Is there anything wrong going with Apple. How can we contact Apple? They are not replying to my emails either.

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, I am unable to receive any tesflight invite email in order to test on my end, can anyone assist with this issue.

Filed: FB23052931 (Feedback Assistant, 2026-06-10) + Apple Dev Support Case 102913469272. Question for the community: Has anyone else hit this and resolved it? TestFlight beta feedback (screenshot submissions) for one of our apps stopped being recorded in App Store Connect at 2026-05-31 17:15:54 UTC. Testers submit screenshot + comment via TestFlight "Send Beta Feedback" — the dialog completes successfully and dismisses with no error — but submissions never appear in the ASC web UI under TestFlight / Feedback / Screenshots or in the App Store Connect API endpoint GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions. meta.paging.total has been frozen at 882 for 10+ days. Verified live by submitting two screenshots from a current TF build today and confirming the API total did not increment seconds later. The betaFeedbackCrashSubmissions endpoint is also stale on this app (last entry 2026-05-03), which makes me think it's the whole beta feedback ingestion pipeline for this app record, not screenshot-specific. Minimal repro: 1) Install a current TestFlight build (any from a current train, processed VALID, internalBuildState IN_BETA_TESTING, delivered to a tester group). 2) Take a screenshot inside the app. 3) From the share sheet, tap "Share Beta Feedback". 4) Add a comment, tap Submit. Dialog completes successfully. 5) Query the App Store Connect API: GET /v1/apps/{id}/betaFeedbackScreenshotSubmissions?limit=200. meta.paging.total is unchanged. data[0].attributes.createdDate is unchanged. Developer-side causes I've already ruled out: Build processing: all 10 most-recent builds are VALID with internalBuildState IN_BETA_TESTING and were delivered to both internal and external tester groups. Per-group Tester Feedback toggle: verified ON for both groups in the ASC UI. App entitlements / Info.plist: no changes in the 30 days prior to the cutoff. Tester membership: verified active. The tester used in the repro is Account Holder on the team. ASC API key: the same key successfully retrieves the 882 historical submissions. Read auth is intact; only writes from the device side fail to land. App Privacy: configured and submitted. What I've already filed: Feedback Assistant: FB23052931 (filed 2026-06-10, Area: App Store Connect, Incorrect/Unexpected Behavior) Apple Developer Support (Distribution / TestFlight email channel): Case 102913469272 (filed 2026-06-10, cross-references FB23052931) What I'd love to hear from the community: Have you seen this exact pattern (sharp cutoff date, total frozen, no error on submission)? Did it eventually resolve on Apple's side, and if so what was the rough turnaround? Is there anything you tried on the developer side that actually re-enabled ingestion (re-promoting a build to groups, regenerating an ASC API key, anything)? Anyone on a thread where an Apple Frameworks Engineer responded to this class of bug? I'm aware of older threads going back to 2019 (thread 122295) with similar symptoms but no Apple engineer response. Hoping to surface a more recent path forward. Thanks.

Hello to the community. I’m hoping someone here can help me. we have been developing our mobile app with a 3rd party contractor. I used to provide feedback through TestFlight screen shot program and it was great. Straight from my iPhone to the dev team. Screen shots with descriptions of the problem. they recently transferred the app to our account and I think since then we can no longer receive the feedback. in fact, last week I spent 2 hours reviewing the app. Sending tons of screen shot feedback with comments. Thinking they were receiving them. But nothing. when we log into our feedback portal I only see feedback from 70 days ago. And nothing from recent. I made sure that feedback is welcome ( see screen shot ) i tested individual feedback test and got nothing. here are my questions. Is there a way to recover that feedback. Where is it going ? How can I get this feature working properly again so I can effectively and efficiently review the app and provide feedback to the developers.

We have a managed iOS app, distributed to managed iPhones through Apple Business Manager, and we are offering a TestFlight version. When users install a TestFlight Version, it is relatively quickly replaced by the current release. Is there a way to prevent this?

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.

Hey everyone, hoping someone here has seen this before because I'm losing my mind. I uploaded my first TestFlight build yesterday and added two internal testers. Both of them accept the invite fine, but the moment they tap Install in the TestFlight app, they get: ▎ "The requested app is not available or does not exist" My developer account is about a month old, but yesterday was the first time I actually pushed a build to App Store Connect. I've spent the last several hours triple-checking every setting and as far as I can tell, everything looks right: Free Apps Agreement is Active under Business Price Schedule is set to USD 0 (Free) App is available in 175 countries Bundle ID matches between my project and App Store Connect Build metadata shows App Uses Non-Exempt Encryption: No (and the same key is in my Info.plist) The build status in my Internal Testing group "Team" is Testing with the green checkmark Both testers were added under Users and Access first, then to the internal group One tester shows "Accepted" status, but the Devices column is still empty — so the invite went through but the install never actually reaches the phone Tester is on iPhone running iOS 26, my build's minimum iOS is 18.0, so that's not it I've uploaded 3 builds at this point (1.0.0 (2), (3), and (4)) — all of them show "Testing" in the group. None of them install. Things I've tried so far: Force-quitting and reopening TestFlight on the tester's phone Resending the invite Disabling Vision Pro testing in the group settings (there was a "Version 1.0 is not compatible" warning on the Vision Pro section in Pricing & Availability) Asking a second person to try — same error Any pointers appreciated. I've been at this for hours and I'm out of ideas. Happy to share screenshots or more details if it helps. Thanks 🙏

Hi friends, Since yesterday, I'm not able to download any of my apps from TestFlight (while I can for others developers). I'm searching since 2 days now about the reason and I think I've tried everything, so I'm asking if you might have an idea... It occured after adding subscriptions to one of my apps, then I did all of these: Check all contracts on my apple developer account Verify my apple ID in internal testers Install / Uninstall TestFlight app Remove / Re-add myself as tester Try new builds My apps are listed on the Apple Store and not removed from Sales. Did I miss something? The error is mysterious... I also contacted Apple, I'm waiting for their answer. Thank you 🙏

Hello! I submitted a game to testflight yesterday, I sent to a few friends. Everything is running great, but it looks very cramped in the top (logo is crammed ) all buttons are still reachable, it just looks smushed. is TestFlight exactly how the game will look on phones like mine? I know I have it set up to automatically scale.

I just deployed an app, and enrolled few users to test the app via TestFlight, but they are not receiving the e-mail invite. any recommendations on how to troubleshoot this ?

Anyone is experiencing this issue? Today without any reason we can think of, all of our builds were expired on Testflight. Without knowing what happened, then we tried to add a new build, that it it seems to be in good shape on Testflight, even with the mark green meaning is ready to be tested. Even though, by trying to install the app on iOS using TF, we are getting a message saying "The requested app is not available"

Hello, Our iOS app’s TestFlight external testing build has been stuck in “Waiting for Review” for several days. This is for TestFlight External Testing, not an App Store public release submission. We have already provided the Beta App Review Information, including review notes, test instructions, contact information, and a working demo account. Current situation: App name: Linic Platform: iOS Submission type: TestFlight External Testing Status: Waiting for Review Submitted date: June 4 ~ June 5, 2026 Build number: 1.4.2(8)、1.4.3(9) Bundle ID: com.lincept.linny Beta App Review Information: already updated Demo account: provided in App Store Connect We would like to understand whether this is currently expected queue behavior, whether TestFlight external beta reviews are experiencing delays, or whether there is any additional information we should provide to help the review proceed. Has anyone recently experienced a similar delay with TestFlight External Testing builds stuck in “Waiting for Review”? If so, did contacting Apple Developer Support or submitting an expedited review request help? Thank you.