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

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.