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

Since 23 September 2026, TestFlight has stopped working for our app, and nothing on our side fixes it. It looks like the same beta contract problem described in threads 814565 and 821498. App Obaloot: Apple ID 6815224192, bundle ID com.ossaritas.obaloot Version 1.0.0, not released yet (Prepare for Submission) What happened On 23 Sep 2026 at 17:29:53 UTC, builds 1.0.0 (56), (57) and (59) all expired at the same second. Nobody on our team expired them. Builds 56 and 57 had been approved in Beta App Review that same day. Since then, no tester can install any build, internal or external. Builds 60, 94 and 148 process as Valid and are available to our internal group, but tapping Install in TestFlight shows: "Could not install Obaloot. The requested app is not available or doesn't exist." Submitting a build for Beta App Review through the App Store Connect API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING: "Beta contract is missing for the app." This happened for build 60 on 23 Sep and build 94 on 24 Sep. Already checked All agreements under Business are Active, nothing is pending, and the membership is active. Test Information (description, feedback email, review contact) and the beta license agreement are filled in. Export compliance is set (no non-exempt encryption). New builds fail the same way. Deleting the app from the device before installing gives the same error. Apple Developer System Status shows no outage. Support Developer Support case: 102974806458 Could someone from the TestFlight team check our team's beta contract and restore it? I'm happy to share any details privately.

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “Your app could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “App could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Hello, I’m experiencing a sudden TestFlight issue affecting multiple unrelated apps under the same Apple Developer account/team. Several TestFlight builds across my apps suddenly changed to Expired at the same time, even though many of them were uploaded only a few days ago and were nowhere near the normal 90-day expiration period. I also uploaded a brand-new build to check whether the problem was related only to existing builds. The new build: Processed successfully Appears normally in App Store Connect Appears in the TestFlight app Shows 90 days remaining Shows the Update button However, when I try to install or update it, TestFlight immediately displays: “The requested app is not available or doesn’t exist.” So build upload and processing appear to work correctly, but TestFlight distribution/install does not. Since multiple completely separate apps under the same developer team became affected at approximately the same time, this appears to be an account/team-level TestFlight issue rather than an issue with a specific Bundle ID, provisioning profile, certificate, project, or individual build. I have also seen recent reports mentioning: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING and TestFlight Beta Contract issues. Has anyone confirmed whether this is currently an Apple-side TestFlight backend / Beta Contract issue? If Apple staff see this post, could you please check whether TestFlight beta distribution provisioning or the Beta Contract for affected developer teams needs to be re-provisioned? I can provide screenshots showing: Existing builds suddenly marked as Expired A newly uploaded build showing 90 days remaining The installation error Thank you

I am building my 1st App. I was able to push my App in my iPhoen and also to some internal testers until now. I made some changes in my App in XCode and pushed the App Build to internal testers (including my iPhone). First I removed the old App version from my phone due to this issue. Now I can see the status of my App is Testing, I get email notification of Test flight. I can see the App in Test Flight in my phone. but when I click on the 'Install' button, it says - Could not Install [App Name]. The requested app is not available or doesn't exist. I tried several options like building the new version. but me and all other internal testers are having the same issue. I build the App in Flutter so I am testing in Andriod phone also. I am able to test he new build in Andriod phone without any issue. But in Iphone it is filing since last 4-5 days. I created a service request (Case ID 102974814384) last week but no response from Apple support. I am very frustrated as it is my 1st App and I am losing confidence thinking what will happen if such issues keep coming after I go live.

The UI only says "There was an error processing your request". The network response is: POST /iris/v1/betaAppReviewSubmissions → 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING In Business → Agreements, all agreements are active and there is nothing left to accept. The build is processed and valid. Re-uploading, bumping the version and creating a new app version change nothing, so it looks like the account's beta contract flag didn't update after renewal. We contacted Developer Support over a week ago (Distribution → TestFlight) and haven't heard back. Could someone from Apple check the account's beta contract status or pass this to the App Store Connect team? Error ID: c9e61135-7a2f-4f52-bc39-bd3437d94440

It's been 6 days since I purchased it, and other forums are telling me it takes about two days to approve it. I'm working on a project for a club and they are in need of my project and this is the only way I can distribute this to them.

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

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.

SUMMARY TestFlight installation and external beta review submission are blocked for ITNRY. External submission returns ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING through both the App Store Connect website and the public App Store Connect API. Apple Developer Support case: 102968975728 Submitted: 19 September 2026 I have not yet received a response. APP AND BUILD DETAILS App: ITNRY: Private Trip Planner App Store Connect app ID: 6747810116 Bundle ID: com.c0defr1ft.ITNRY Version 5.5, build 1: Build ID: ace0e146-a828-49cd-8773-351f12dfc4b0 buildAudienceType: APP_STORE_ELIGIBLE processingState: VALID expired: false Version 5.5, build 2: Build ID: 4cb01458-8df0-44f5-810c-5a9769a2980d buildAudienceType: INTERNAL_ONLY processingState: VALID expired: false The external review submission described below uses build 1, NOT the internal-only build 2. STEPS TO REPRODUCE — APP STORE CONNECT Open ITNRY → TestFlight. Add version 5.5, build 1 to an external testing group. Complete the requested test information. Select Submit for Review. Actual result: “There was an error processing your request. Please try again later.” The failed network response contains: HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING “Beta contract is missing for the app.” STEPS TO REPRODUCE — PUBLIC API Send an authenticated request to: POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions Request body: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "ace0e146-a828-49cd-8773-351f12dfc4b0" } } } } } Actual response: HTTP 422 { "errors": [ { "id": "d916bbd9-4cff-4a05-8f0c-7432ec8db5d3", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } Request ID: EYMVAZWCULILULIFKLQDUQ5DXI Timestamp: 19 September 2026, 17:32:43 UTC ADDITIONAL SYMPTOM — INTERNAL TESTFLIGHT The build is visible in TestFlight, but installation fails with: “The requested app is not available or doesn’t exist.” The iPhone’s Media & Purchases account matches the account assigned as an internal tester. TestFlight has also displayed an old email address previously associated with the same Apple Account. It is unclear whether this is related to the contract error. DIAGNOSTIC CHECKS ALREADY COMPLETED GET /v1/apps/6747810116/betaLicenseAgreement returns HTTP 200 and the following betaLicenseAgreements resource: 8289bafa-8347-4a7a-a2b4-86b580758220 Listing betaLicenseAgreements filtered by this app also returns that resource. Its agreementText was initially empty. As a troubleshooting attempt, I successfully populated it through the API and verified that the change persisted. External submission still returned the identical BETA_CONTRACT_MISSING error afterward. This establishes that the per-app betaLicenseAgreement resource exists. It does not establish whether that resource is the contract referenced by the submission error. EXPECTED RESULT An authorized internal tester should be able to install the assigned build. An eligible external build should submit for beta review, or App Store Connect should identify a specific outstanding requirement and provide an actionable way to resolve it. IMPACT AND REQUEST The issue blocks TestFlight installation and external beta review submission. Please investigate the contract validation/provisioning state for this app/account, identify which contract is reported missing, and advise whether any developer action is required. Please also determine whether the internal installation failure shares the same cause. Please link this report to Developer Support case 102968975728.

I’m validating the officially supported distribution path for an independent watchOS app. Target device Apple Watch Series 6 GPS + Cellular watchOS 26.6 Configured using Apple Watch For Your Kids / Family Setup The Watch belongs to a child Apple Account Managed from the parent/guardian’s iPhone 11 running iOS 27.0 The child does not have their own iPhone Direct development deployment from Xcode is not available in this configuration on my setup. The Family Setup Watch does not appear as a development destination / CoreDevice device and does not expose Developer Mode. Main question Does TestFlight officially support installing a watchOS-only or independently installable watchOS app onto an Apple Watch configured with Apple Watch For Your Kids / Family Setup? If yes: Is installation initiated from TestFlight on the parent/guardian iPhone that manages the Family Watch? Should the Family Setup Watch appear as an eligible Apple Watch target inside TestFlight? Should the child Apple Account or the parent/guardian Apple Account be added as the TestFlight tester? Are there any additional restrictions or requirements specific to Apple Watch For Your Kids / Family Setup? Is Developer Mode required on the Watch for TestFlight installation? I’m specifically asking about an officially supported TestFlight/App Store Connect distribution path, not Ad Hoc distribution, manual IPA installation, private APIs, or unsupported workarounds. Thank you.

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_utc source build_number method url http_status error_code error_id x-apple-jingle-correlation-key x-apple-request-uuid x-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:-1::::prod failures-422.md failures.jsonl failures.md session.sanitized.har

Hi, Since mid-September 2026 TestFlight is completely blocked for my account, even though my app is live on the App Store and all agreements are active. Symptoms No tester (internal or external) can install any build. TestFlight shows: "Could not install Beavo. The requested app is not available or doesn't exist." A newly added internal tester sees "No Builds Available" in App Store Connect. Submitting any build to Beta App Review fails with HTTP 422: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Request UUID: 911b4c7a-1c7f-5b75-5c49-bcf26292fb18 (24 Sep 2026, 16:16 GMT) What I've verified Paid Apps Agreement: Active (Jun 2026 – Jun 2027) Free Apps Agreement: Active (regenerated Aug 19, 2026) Bank account, W-9 tax form and DSA compliance: Active I'm the Account Holder / Admin Builds (1.4.0 (13) through 1.5.0 (20)) are VALID, not expired, min iOS 26.0 ITSAppUsesNonExemptEncryption = NO is in Info.plist (no Missing Compliance) Test Information complete (description, feedback email, marketing and privacy policy URLs, Beta App Review contact) The last builds approved for external testing were in July 2026; nothing since then can be submitted This looks like the same backend issue reported in threads 814565 and 815885, where the Beta Contract entity was not re-provisioned after the agreements were regenerated, and it was fixed by an Apple engineer manually. App details App: Beavo – Apple ID 6781859321 Bundle ID: com.invntio.beavo Team ID: P4C48NFAHR I've also opened a case with Developer Support. Could someone from Apple please re-provision the Beta Contract for this account/app? Thanks!

Hi! Is there a way to cancel a subcsription purchased via Testflight? The subscription is not displayed in Apple account's Apps & Purchases.

Hi everyone! I’m looking for testers for Lattice LEap, my iOS app. You can install the beta through TestFlight here: https://testflight.apple.com/join/GafJ2BTW I’d really appreciate feedback on usability, bugs, performance, and anything that feels confusing or could be improved. Thanks for helping me test it!

Hi Apple Developer Support team, We are encountering a validation failure when uploading an iOS app build to App Store Connect. The upload fails with the following error: Validation failed This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable. (ID: 9a27ff00-bf7c-4c8d-9980-f11f7ea6430f) Additional error details: Error Domain=IrisAPI Code=-19241 "Validation failed" UserInfo={ status=409, detail=This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable., id=9a27ff00-bf7c-4c8d-9980-f11f7ea6430f, code=STATE_ERROR.VALIDATION_ERROR, title=Validation failed, NSLocalizedFailureReason=This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable., NSLocalizedDescription=Validation failed } Our app’s deployment target is set to iOS 12.0, and the generated bundle contains: MinimumOSVersion = 12.0 This value has been accepted in previous uploads, but the latest upload was rejected during validation. Could you please help confirm: Is iOS 12.0 still an acceptable minimum deployment target for newly uploaded iOS app builds? Has there been any recent App Store Connect validation rule change related to MinimumOSVersion? Are there specific bundle types, SDK versions, or build settings that may cause MinimumOSVersion = 12.0 to be considered invalid? Any guidance would be appreciated. Thanks.

BoltSense is a puzzle game where you tap bolts off a real 3D V8/inline-4 engine and sort them into color/shape-matched trays as it tears itself down layer by layer. Solo-built, first time opening it up to anyone outside my own family. I know this is flooded market; I got tired of pay to win platforms and wanted to build something better. Feedback I'm especially looking for: First few minutes — is it clear what to do with zero instructions? Where did you get stuck, if anywhere? Bolt shapes — can you tell hex bolts from round ones apart quickly while playing, or are you mostly going by color? Difficulty — does the first engine feel too easy, too hard, or about right for an opening puzzle? Considering that I have tested this with my 7 and 9 year old and they picked it up pretty easily following minimal instruction. Crashes, hangs, visual glitches — and what iPhone/iOS version you were on when it happened please! Public link: https://testflight.apple.com/join/YMpvN6bP Appreciate anyone willing to give it a shot — feedback straight through TestFlight works great for me. *I only have this set at 1000 testers I'm hopeful to see 10-20 maybe! Thank you!

Typical is an iOS app with a custom keyboard extension for high value salespeople: luxury real estate, yachts, cars, watches. The app stores clients, assets and conversation history. The keyboard shows the relevant client context inside WhatsApp while the user types, so they can answer specific questions without leaving the conversation. Feedback I am looking for: Keyboard onboarding: enabling the keyboard and granting Full Access. Is the warning off putting? Is the reason for Full Access clear enough? Client recap screen: is it understandable the first time it appears? Stability and performance: crashes, freezes, input lag in the keyboard. F eedback through TestFlight is preferred. https://testflight.apple.com/join/5yx5EDg5

During dev time i've done some tests with app never releasedWhen i delete these apps, they move to "removed apps" and this prevent to reuse some App IDHow can I permanently delete an app so I can reuse an App ID?