Hello, I am experiencing a serious TestFlight issue that began immediately after I removed some testers from an External Testing group. Right after removing those external testers, all existing TestFlight builds for my app were suddenly marked as Expired, even though they were still within the normal 90-day TestFlight validity period. I did not manually expire any build. Removing an external tester should only revoke that tester’s access and should not affect the status of any TestFlight build. After the mass expiration, I uploaded a replacement build. The new build uploaded and processed successfully in App Store Connect, but I could not add or submit it for External TestFlight Beta App Review. App Store Connect incorrectly displays the following message: Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership. However, my account currently shows: Account type: Individual — Account Holder Apple Developer Program membership: Active Apple Developer Program License Agreement: Accepted Free Apps Agreement: Active No pending Apple Developer Program agreements Replacement build uploaded and processed successfully I inspected the failed App Store Connect network request and found the actual backend error: POST /iris/v1/betaAppReviewSubmissions HTTP 422 Unprocessable Content { "errors": [ { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } The exact sequence was: External testers were removed from the External Testing group. All existing TestFlight builds suddenly became Expired. A replacement build uploaded and processed successfully. The build could not be submitted for External Beta App Review. The backend returned ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. I have found reports from other developers describing the same sequence after removing external testers, including all TestFlight builds unexpectedly expiring and TestFlight distribution no longer working. This appears to be an account or team-level TestFlight backend issue in which the Beta Contract or distribution state becomes detached after modifying external testers. I have already contacted Apple Developer Support and provided the private account, app, request, and error identifiers through my support case. Could an Apple engineer please confirm whether this is a known backend issue and whether the TestFlight Beta Contract needs to be re-provisioned or re-attached? Has anyone else experienced this exact issue after removing external testers? If Apple resolved it, what action was required on the backend? Thank you.

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.

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.

I’m experiencing what appears to be a team/account-level TestFlight backend issue, and it is currently blocking my development workflow. Team ID: TJ6F83PA4W What happened All existing TestFlight builds across my apps suddenly became Expired / unavailable. This happened across the developer team rather than to one particular app or build. I then uploaded a completely new build to determine whether the previous builds had simply been reset or invalidated. Test app: RESON | See the frequency. Apple ID: 6799940431 Version: 1.0.0 Build: 2 The new build: Uploaded successfully Processed successfully Appears normally in TestFlight Shows a fresh 90-day testing period Has an active Install button But installation immediately fails with: Could not install RESON | See the frequency. The requested app is not available or doesn’t exist. So this does not appear to be normal build expiration. A completely new and successfully processed build is also affected. Troubleshooting / support I have already opened an Apple Developer Support case: Case ID: 20000133520102 I’ve contacted Developer Support multiple times by email and also requested/spoken through phone support, but the issue remains unresolved and is now blocking my TestFlight workflow. I have intentionally not started changing certificates, provisioning profiles, Bundle IDs, or repeatedly uploading replacement builds because the symptoms affect the entire team and appear to occur at the TestFlight distribution stage. I’ve also seen reports from other developers describing similar symptoms, including references to BETA_CONTRACT_MISSING / missing Beta Contract backend state. I cannot confirm that this is the cause on my account, but the symptoms appear similar. Question for Apple / other developers Has anyone experienced this exact combination? All TestFlight builds unexpectedly expire → new builds process successfully → builds appear available for 90 days → installation fails with “The requested app is not available or doesn’t exist.” If someone from App Store Connect / TestFlight engineering sees this, could you please advise whether the Beta Contract / TestFlight distribution provisioning state for the Developer Team needs to be checked or re-provisioned server-side? Any confirmed workaround or escalation path would be greatly appreciated.

A build has been uploaded to TestFlight, and we have existing Internal Testing groups that have worked successfully in the past. However, when I click the blue + button under Groups, all groups are disabled and cannot be selected. The same issue occurs with a newly created group. I’m an Admin and have permission to manage testers and groups. Build Distribution is set to Automatic for Xcode Builds, as it was previously when this worked without issue. Is there a known workaround or setting that could resolve this? 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

I've had a DTS/support ticket open since August 1st with no response yet, so posting here in case anyone has seen this or has a workaround. Symptom: Installing from TestFlight fails with: "Could not install [App Name]. The requested app is not available or doesn't exist." This happens across three separate, unrelated apps in the same Apple Developer account: A brand-new app (bundle ID re-registered under a new identifier after the original app record was deleted from App Store Connect) Two existing, previously-working apps that have nothing to do with the new one One of the existing apps also had its TestFlight build expire noticeably earlier than the stated 90-day testing window — not explained by a device clock issue (confirmed device date/time is correct and set automatically). Already ruled out: Device Date & Time (automatic, correct) Screen Time / Content & Privacy Restrictions → Installing Apps (set to Allow) Fully deleted + reinstalled the TestFlight app itself (not just force-quit) Confirmed tester status shows "Accepted" in App Store Connect for the affected builds Confirmed binary validated, export compliance answered, age rating completed, Developer Program agreements active Confirmed bundle ID correctly registered in the Developer Portal Since this spans multiple unrelated apps on one account rather than a single misconfigured app, it looks like a distribution-service-side issue tied to the account/team rather than anything fixable on our end. Has anyone run into this pattern (account-wide TestFlight install failures, or early build expiration) recently? Any known fix, or is this purely an Apple-side bug that needs their infra team to look at?

Testflight has stopped updating its version after uploading new build.

Hello, We are unable to use TestFlight for our app. Every attempt to attach a build to a testing group fails server-side with a 422. Error (from the App Store Connect network response): { "errors" : [ { "id" : "684c7800-6d62-43f9-8447-e30b83ebaf8c", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } App details: App name: Discipline 366 App ID: 6782504331 Bundle ID: com.gero.discipline366app Account type: Organization Existing Apple Support case: 20000118718501 (Distribution / TestFlight) Symptoms: Adding a build to an External Testing group or public link returns the 422 above. The failure is server-side in App Store Connect — no invitation is ever generated and nothing reaches a device. App Store Connect displays: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." This message is inaccurate — see below. "The requested app is not available or doesn't exist" in the TestFlight app. Builds uploaded 2–3 days prior show as Expired, well inside the 90-day window. What we have verified: Apple Developer Program membership is Active, renewed approximately two months ago. Membership details shows a valid expiration date. The renewal prompt in App Store Connect directly contradicts this and appears to be a generic rendering of the underlying BETA_CONTRACT_MISSING state rather than an accurate diagnosis. Under Business > Agreements, Tax, and Banking: Paid Apps Agreement Active, Free Apps Agreement Active, banking information complete, tax forms complete and active. No pending agreements and no action banners anywhere in the account. Confirmed the Account Holder is the one signed in; agreements were reviewed under that Apple Account, not an Admin or Developer role. Production uploads work normally. The build processes and appears in App Store Connect without issue. No changes to distribution certificates or provisioning profiles around the time the failure began. No incidents reported on the Apple System Status page for App Store Connect / TestFlight. Timeline: The failure began on 2026-07-24 and has been continuous since. It reproduces with every build, old or new — re-uploading changes nothing. TestFlight worked normally on this account before that date. A support case was opened at the time and has not produced a resolution. Question: Given that every developer-side prerequisite is satisfied, this looks like a missing or detached beta contract record on Apple's backend for this team. This is not a state we can clear from App Store Connect. Could the beta contract record for App ID 6782504331 be inspected and re-provisioned server-side? If it is re-provisioned, please confirm whether we should wait before uploading a new build — I have seen 48 hours mentioned in a similar thread. I note that several other threads in this forum describe the identical symptom set on accounts with all agreements Active, which suggests this may not be isolated to our team. Thank you.

I’m having a strange TestFlight issue with one of my builds. Version 1.0.0 has two builds. Build 1 works normally in TestFlight, but Build 2 is unavailable to every tester I’ve tried. Build 2 was uploaded successfully, and App Store Connect shows it as “Testing”. I also received Apple’s email saying version 1.0.0 (2) is available to test. However, Build 2 still can’t be accessed through internal testing, external testing, or a public link. For internal testing, I assigned only Build 2 to the group, but TestFlight shows “No Builds Available”. I tried the same with an external testing group and got the same result: “No Builds Available”. The public link is enabled with no device or OS restrictions, but new testers see “This beta isn’t accepting any new testers right now.” I’ve already tried removing and re-adding testers, recreating testing groups, removing and re-adding Build 2, disabling and re-enabling the public link, resending invitations, removing the app from the device, stopping testing in TestFlight and joining again, and testing with Build 2 as the only build assigned. None of that changed the result. Build 1 still works normally for the same app. Build 2 details: Version: 1.0.0 Build: 2 Minimum iOS version: 15.0 Device family: iPhone Architecture: arm64 The test device meets the compatibility requirements. There is also an upload warning: 90737: Missing Document Configuration The same warning appears on both Build 1 and Build 2, but Build 1 is distributed normally. Has anyone seen a TestFlight build that shows as “Testing” and generates Apple’s “available to test” email, but still isn’t available to internal testers, external testers, or public-link testers? Could there be some server-side TestFlight distribution state or App Store Connect setting causing this? Thanks.

We are experiencing an issue with our TestFlight build The build was successfully uploaded to App Store Connect and is available for internal testing. Our internal testers can see the build in TestFlight, but when they attempt to install it, they receive the following error: "Could not install Game. The requested app is not available or doesn't exist." This issue occurs for all internal testers. The build upload completed successfully, and the build is assigned to the internal testing group. We are unable to determine the cause of this issue. Could you please help us identify whether there is any missing configuration or any other requirement that could be preventing the app from being installed?

I have a app running in test flight that keeps expiring how do I get it to finally just be on the App Store

Hello guys I’m unable to delete the Test Information and Beta App Information sections on Apple Store Connect. I need to remove them because the app transfer process requires it. I’ve already expired all builds, removed all testers and groups, and tried every possible solution I could find online, but nothing worked. I also contacted Apple Support, but the issue hasn’t been resolved. What should I do next?

Todos os meus apps estão informando no TestFlight que eles ão existem ou não estão disponível, não sendo possível ser feito o download dos apps testes pelo TestFlight.

Hello, For several months, I have been unable to install any TestFlight build submitted by my Apple Developer team. All builds archive, upload, and complete processing normally. They appear as Valid in App Store Connect and are visible in TestFlight with an Install button. However, tapping Install fails immediately with: “Could not install [app name]. The requested app is not available or does not exist.” Current example: App: TopGestor Cliente Apple ID: 6799197509 Bundle ID: com.topgestor.cliente Version / build: 0.1.0 (3) Platform: iOS, arm64 Minimum iOS: 15.1 This is not limited to this app; it also affects other apps submitted by the same team. Reinstalling TestFlight, restarting the device, and submitting fresh builds did not resolve it. Could an Apple engineer please verify whether there is an account-level TestFlight distribution, build availability, or beta contract association issue on the backend? I have also opened an Apple Developer Support case.

FileFerry is a native macOS file transfer client. It speaks FTP, FTPS (explicit AUTH TLS), SFTP, WebDAV and SMB, and opens a full SSH terminal on the same connection. Written in SwiftUI and AppKit, sandboxed, no third-party services. Requires macOS 14.6 or later. Free during the beta. https://testflight.apple.com/join/yY7JpHBP What I would most like tested The protocol side, against servers I have no access to: FTP directory listings from servers other than vsftpd and ProFTPD. MLSD is preferred where available; the LIST parser is the part most likely to break on an unusual date or month format, and a line it cannot parse means the file is missing from the table. FTPS against servers that require TLS session reuse on the data connection. vsftpd defaults to requiring it; the app uses separate connections and reports 522 with an explanation rather than failing silently. Self-signed certificates and host key changes. Fingerprints are confirmed once and then checked every session; a changed one refuses the connection, with no override. SMB shares with unusual permissions or on non-standard ports. Also worth breaking Transfers are retried three times, then verified — SHA-256 over SSH for SFTP in both directions, file size for FTP uploads. Anything that still fails goes on a list that survives quitting the app, so a connection lost part way through a large directory can be picked up afterwards. Nothing on the server is ever deleted automatically. Feedback through TestFlight reaches me directly. Bug reports with the session log are the most useful — the app shows the full wire dialogue and can write it to a file.

I’m looking for about 15 additional iPhone/iWatch users to test SomataQuest, an early-stage fitness app that uses Apple Health data to help users understand their recent training, recovery, and readiness for today’s activity. Learn more: https://www.nexuspointinnovations.com/somataquest TestFlight: https://testflight.apple.com/join/BjXUh9bj I’d especially appreciate testers trying the following: Connect Apple Health and complete the initial setup Check whether the readiness score and its explanation make sense Review whether the app represents your recent workouts and activity accurately Evaluate whether the suggested training intensity feels reasonable Report anything confusing, incorrect, slow, or broken The app currently works best for people who regularly record workouts, sleep, heart-rate, or activity data in Apple Health. Feedback can be submitted through TestFlight or posted in this thread. This is an early beta, so candid feedback—especially about what is unclear or not useful—is very welcome.

I have run into this problem today. I distribute a macOS app to internal testflight group from Xcode. Upload to App Store Connect succeeds. I receive the email that a new TestFlight build is available to test in TestFlight. The new build shows in TestFlight app. When I try to install the build I get the following error dialog. Could not install App. TestFlight is currently unavailable. Try again. I have submitted feedback FB24059381 with additional information.

Hi everyone, We've been stuck on this issue for several days and would really appreciate any guidance from anyone who has encountered this before. Issue Our app uploads successfully to App Store Connect, appears in TestFlight, and the build status is Ready for Internal Testing. However, every internal tester receives the following error when trying to install the app through TestFlight: Could not install . The requested app is not available or doesn't exist. Environment Apple Developer Program: Individual Distribution: Internal TestFlight Framework: React Native (Expo SDK) Build Service: Expo EAS Build Submission: Expo EAS Submit Platform: iOS What we've already verified The app builds successfully. The IPA is signed successfully. Build upload to App Store Connect succeeds. Build processing completes successfully. The build is assigned to an Internal Testing group. Internal testers have accepted the invitation. The bundle identifier is correct. Distribution certificate and provisioning profile are valid. We generated fresh builds and submitted them again. We recreated the App Store Connect app and submitted a new build. We also regenerated signing credentials where applicable. The issue persists across multiple builds. Additional Information During eas build, Apple successfully authenticates, registers the bundle identifier, creates the distribution certificate and provisioning profile, and the build completes without errors. eas submit also completes successfully, and the build appears in TestFlight. The failure only occurs when attempting to install the app from the TestFlight app. Error Could not install . The requested app is not available or doesn't exist. Has anyone experienced this issue recently? Is this likely a TestFlight/App Store Connect backend issue, or is there any App Store Connect configuration that we may have overlooked? And this is our active case id for the support: 102930164003 Any suggestions would be greatly appreciated. Thank you!

My TestFlight build has been in Waiting for Review since June 27, 2026 for more than a month. It was submitted for Beta App Review to enable public testing for external testers. Submission ID: f83d8d76-b239-48a8-8776-e93f4d03d5df Could someone please check whether the submission is stuck or if any additional action is required from my side? Thank you.