TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)

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 @DTS Engineer

I'd be very grateful for any help or advice with my app review.

My app, UniCollab, was rejected, and I fixed everything App Review asked for and replied in App Store Connect. After more than a week with no response, I had to cancel that submission so I could upload a new build with the requested changes and further bug fixes. I understand this has probably put me back at the start of the queue.

I have since submitted an expedited review request, as I have a launch deadline and investors waiting on the release and really pushing me about it.

If anyone from Apple is able to look into this or advise on next steps, the details are:

  • Apple ID: 6811972510
  • Submission ID: 258b9205-1ff6-4e1d-9f10-7a416e9e0212

Thank you very much for your time.

@KJohnson88

Thank you for your post. The thread is about TestFlight not App Review, however as always If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, please ensure that you provide specific reasons why you believe your app complies with the App Review Guidelines.

Additionally, please submit only one appeal per rejection. It is also important to respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal, they will escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they have completed their investigation.

There is a post from the App Review that answers all common questions that you should read before contacting them: https://developer.apple.com/forums/thread/810791

I would recommend to go over all the resources in App Review https://developer.apple.com/help/app-review/

Contact App Review: https://developer.apple.com/help/app-review/after-submitting-for-review/contact-app-review

Hope this helps

Albert  WWDR

Same issue on our team since about October 11, 2026: every TestFlight build of every app on the team fails with "The requested app is not available or doesn't exist", for two internal testers on two devices. Installs worked on this team in spring 2026. Agreements, tax, banking and compliance are all Active, and builds are Complete and Validated. Filed as FB25219279, and Developer Support case 102995664597. Thanks to anyone on the TestFlight team who can take a look.

@DTS Engineer Thank you for taking the time to reply, and apologies for posting in a TestFlight thread. I replied here because I haven't been able to get a response anywhere else, and very few review-related threads seem to not receive an answer.

To clarify, I'm not disagreeing with the rejection, so I don't believe an appeal is the right route. I read the feedback carefully, fixed everything App Review asked for, and checked it many times before replying in App Store Connect and resubmitting.

The problem is that the resubmission then received no response for over a week. Because the required changes were in a new build, I had to cancel that submission and submit the new build with all the fixes. I understand this has put me back in the queue, but it has now been waiting far longer than the usual 24 to 48 hours.

I have already requested an expedited review and sent several messages through the Contact App Review page, but I haven't received a reply. I have a launch deadline and investors waiting on the release, so the delay is causing real problems for my business. I hope you can understand the frustration.

I'm also not the only one. There are many recent posts on the forums from developers whose apps have been waiting a long time for over 2 weeks or even over a month without being reviewed, and without a reply from App Review. If you're able to share why reviews are currently taking so much longer than usual, it would help a lot of us plan around it.

If there is any way to have someone check whether my submission is stuck or needs anything from me, I would be very grateful:

  • Apple ID: 6811972510
  • Submission ID: 258b9205-1ff6-4e1d-9f10-7a416e9e0212

Thank you again for your help.

@DTS Engineer same issue here.

2 of my apps currently show that I have been removed from the testers, checking the AppStoreConnect I noticed, the build are expired (way earlier then 90 days). Abfter submitting again, the installation/update TestFlight reports that the requested app is not available or does not exist…

Reported in: FB25224066

@Freakster Thanks so much for posting the bug number, routing it to the engineering team that will be able to help you with that.

Albert  WWDR

@DTS Engineer Same issue on my team, affecting my whole library (16 apps): the 3 apps in testing show expired builds and new builds fail to install with "The requested app is not available or doesn't exist", and all 13 previously tested apps now show "Build removed". Membership and agreements are active.

Feedback: FB25229662

@DTS Engineer same here;

"The requested app is not available or doesn't exist" not able to test as internal tester; or submit builds for external tests.

Another account with the same symptom. Posting exact timestamps in case the shape helps.

SYMPTOM — identical to the thread. TestFlight lists the build; tapping Install gives "You already have this app installed. Do you want to replace the current app version with the test version?"; confirming gives "Could not install [app]. The requested app is not available or doesn't exist." Ordinary App Store installs on the same iPhone and Apple Account work normally. First observed 18 September 2026.

THE EXPIRY EVENT. On 17 September 2026, builds belonging to unrelated apps on my team were all stamped with an expiration inside a three-minute window — 13:23 to 13:25 PDT — regardless of upload date or app state. Builds never submitted, builds awaiting review, and released builds expired together.

Counted against the App Store Connect API today: 638 builds carry an expiration in that window, out of 1,669 on the account. 383 of them share the single minute 13:24.

Someone upthread reported every build on their team expiring inside a four-second window on 12 August. Same shape, different date.

FRESH UPLOADS DO NOT ROUTE AROUND IT. Builds uploaded from 18 September onward receive a normal 90-day term and still will not install. Worked example — Cowming Home, App ID 6811901318, build 156 (version 1.1.0), uploaded 3 October 2026: processingState VALID, expired false, expiry 1 January 2027, attached to the Internal Testers group, export compliance answered, tester present and state INSTALLED. It will not install.

RULED OUT HERE TOO, matching what others in this thread have found:

  • Developer Program membership is active.
  • Every agreement is accepted — Apple Developer Program License Agreement issued 14 October 2026 and accepted 18 October 2026; Apple Developer Agreement accepted 2015.
  • No fastlane on this machine, and nothing in my own tooling writes an expiry or deletes a build, beta or prerelease resource. The only PATCH it makes to a build sets usesNonExemptEncryption.

I have an open Developer Support case, 102978347817, filed 28 September. The most recent reply pointed me at the Rejection Appeal form, which does not apply — nothing of mine has been rejected.

Filing a Feedback Assistant report now and will post the FB number here.

Filed as FB25242217 — area TestFlight, with the 17 September expiry figures and the Cowming Home example from my post above.

Submitted without a sysdiagnose, since the evidence here is account-side build state rather than a device crash. Happy to attach one if that helps it get picked up.

Same issue here. All my TestFlight apps suddenly expired, and freshly uploaded builds fail to install with “The requested app is not available or doesn’t exist.”

I’ve opened a support case: 103000786508.

@Namregah @ahmedebaid

FYI, I just called the apple dev support and they told me, my access to testflight functions has been automaticaly revoked due to unknown reasons. ("it happens sometimes") He created a ticket and told me it will work within 48hrs.

I hope it works and maybe you can try the same :)

@DTS Engineer, filed as FB25247970 (area TestFlight). Developer Support cases: 102999662057, 103001563221 and 103001611411.

The expiry event. On 16 October 2026 at 06:15:05 PDT, every build uploaded on 15 October was given the same expirationDate, about one day after upload. That was also the first day of our new membership year. The last successful TestFlight install was on 15 October (app 6823172521, build 2026.1015.1343).

Fresh uploads don't work around it. New builds get a normal 90-day expiry, process as VALID / Ready for Beta Testing, and still won't install:

  • 6823172521 (com.questapp.mobile): every build.
  • 6824002784 (com.tinyquest.app): a brand-new app record created after the problem started. Build 2026.1019.1141, VALID, in an internal group with access to all builds.
  • 6748294968 (com.gregorylime.somni): a separate, older app record. A fresh build 26, made with Xcode 27 and the iOS 27 SDK, fails the same way.

Already ruled out:

  • Membership is active, and all agreements are active and accepted.
  • All apps are "Prepare for Submission". None was ever released or removed from sale. All are available in 175 countries or regions.
  • The tester is the Account Holder, with the same Apple Account in TestFlight and Media & Purchases. Two different iPhones fail the same way.
  • We expired all builds, removed and re-added testers, and uploaded fresh builds.
  • We created a new Apple Distribution certificate and a new App Store profile.
  • Development and Ad Hoc builds of the same apps install and run fine on the same iPhones.

Freakster's call above suggests TestFlight access gets revoked at the team level ("it happens sometimes"). That matches what we see: the problem follows the team, not an app, build, certificate or device. Could someone on the TestFlight team check team V294T9786Z? Thank you.

Same issue for my team (Team ID 4ZUS8ZLZD8), starting Oct 20, 2026. The TestFlight builds of all my apps switched to "Build Removed" at about the same time.

New builds (Xcode 27.1, iOS 27.1 SDK) process fine ("Valid", "ready to test" email), but every install fails with "The requested app is not available or doesn't exist." The same archive installs and runs fine via Xcode / devicectl (development signing). Device: iPhone 15, iOS 27.0.1.

Agreements took effect Oct 13 / Oct 16 and were accepted Oct 18; membership active until January 2027. Already tried: re-adding myself to the internal group, reinstalling TestFlight, signing out/in, restarting.

Feedback: FB25271158. Developer Support case: 103003744026.

@DTS Engineer Same account-wide issue on my team. Team ID 95MF867832 (individual account, I am the Account Holder).

  • On 19 Oct 2026 at 06:13 PDT every TestFlight build on the team expired at the same second (apps 6819072253 and 6748716751).
  • A new build uploaded on 20 Oct (VALID, 90 days) returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING on POST /v1/betaAppReviewSubmissions. Still failing on 22 Oct.
  • Internal testers cannot install: "The requested app is not available or doesn't exist".
  • All agreements Active, nothing pending. The Paid Apps Agreement was activated on 13 Oct 2026.

Feedback: FB25290077
Developer Support case: 103005423668

Could you please route it to the TestFlight team? Thank you.

Same problem here, filed as FB25297487 with a device log archive attached.

  • Internal tester (the Account Holder) cannot install a new build that App Store Connect reports as VALID and IN_BETA_TESTING; TestFlight shows "The requested app is not available or doesn't exist."
  • The device log shows why: TestFlight's POST to testflight.apple.com/v2/accounts/.../apps/<app id>/builds/<build id>/install returns HTTP 404 (X-Apple-Jingle-Correlation-Key AEAFHTKE5DYNZR3BOVNKCBXOZY, 2026-10-23 14:01:21 GMT). So the TestFlight server says the build does not exist while App Store Connect says it is ready.
  • External beta review submission is also rejected: 422 BETA_CONTRACT_MISSING since 2026-10-18, and today a generic 422 "Please try again later". Agreements are active.
  • Earlier builds expired days after upload. Recreating the app record under a new bundle ID did not help.

To collect the device log without a sysdiagnose, connect the iPhone by cable and run pymobiledevice3 syslog collect --start-time <unix time before the install> out_dir, then search the TestFlight process for "host-install" and "code=404".

Same issue here. On Oct 7, 2026 at 13:11:55 UTC every TestFlight build of all eight apps on our team expired within three seconds. Since then 30+ new builds have processed to VALID and been added to our internal group, and every one fails on device with "The requested app is not available or doesn't exist." The device log shows the install request returning 404, then "Error Downloading Install Data".

Filed as FB25300384 with a sysdiagnose, Team ID and App IDs included. We have also opened a Developer Support case.

@Albert , could you route this to the TestFlight team? Thank you.