I'm unable to add a build to an External Testing group in TestFlight. When I click "Add Build" on the group, select the build, fill in the "What to Test" field, and click Submit for Review, I get: "There was an error processing your request. Please try again later." App: Glimpse Meet people (com.salarumer.glimpse) Build: 1.0.0 (14), uploaded Jul 4 2026 Binary State: Validated The build exists in the iOS builds list and is fully validated — the error only occurs on the final "What to Test" submission step when adding it to an external group. The issue is not isolated to this app — I'm seeing the exact same error on a separate app that is already published to the App Store. This rules out a build or metadata issue on my end. I've tried: Approaching from both the group page (Add Build) and the build detail page Different browsers (Chrome, Safari, incognito) Waiting several days (issue started ~Jul 4 2026) Contacted Apple Developer Support (Case ID: 102933411126, no reply in 7 days)

Hi everyone, I'm wondering if anyone else is experiencing the same issue. For the past several days, I have been completely unable to install any of my TestFlight applications. The problem affects every app on my Apple Developer account, not just a single project. Here is what I've verified so far: Builds upload successfully. App Store Connect finishes processing without errors. The builds appear in TestFlight. My certificates and provisioning profiles appear to be valid. I have tested on different networks and users. The issue still persists. The installation simply fails, making it impossible to test my applications. I have already contacted Apple Support but have not yet received a response. At this point, I'm starting to wonder whether there could be an issue with my Apple Developer account or a backend problem affecting TestFlight. Has anyone experienced something similar recently? If you have, did Apple identify the cause or provide a solution? Any information would be greatly appreciated.

Hi, I’m seeing a strange TestFlight issue. My builds process successfully in App Store Connect, appear in TestFlight, and are assigned to internal testers, but installation fails immediately with: “The requested app is not available or doesn’t exist.” What I’ve verified: • builds are processed/completed • apps are visible in TestFlight • internal tester groups are configured • agreements/banking/tax are active This affects multiple apps in the same developer account. The issue started after adding a widget extension and moving to a new Swift-based workflow, so I’m trying to isolate whether this is: • signing/provisioning/entitlements • widget extension misconfiguration • or a backend issue on Apple’s side I’ve already contacted Apple Developer Support and submitted Feedback Assistant reports. Has anyone seen this exact behavior before?

We have an iOS app that's available on Apple silicon Macs via "iPhone and iPad Apps on Mac." We're planning to add a native macOS build under the same bundle ID. Releasing the macOS build replaces the iOS app on the Mac App Store, and existing users are updated to it. What we can't find documented is what happens to their local data container at that moment. 1. Is the container preserved, and can the macOS app reach it? An iOS app on Apple silicon keeps its data under ~/Library/Containers/. A native sandboxed Mac app expects ~/Library/Containers/<bundle-id>/Data/. Containers are also associated with the creating app's code signature, though both our builds would be re-signed by the App Store under the same team. So we can't tell whether the new app would inherit the old container or get a fresh one. Does the replacement preserve the container, or remove it? If preserved, does the macOS app — same bundle ID, same Team ID — get access to it? Is this a supported path? 2. Can this be tested before release? We filed FB21861189 about TestFlight refusing the in-place upgrade — "To install the macOS version of this app on your Mac, first uninstall the iOS app." The response was this is expected in TestFlight. The forced uninstall destroys the container, so TestFlight only ever shows the clean-install case. The path we need to test is the one we can't reach. Is there a supported way to test the App Store replacement before general release? 3. If data doesn't carry over, what's the recommended bridge? If so, we'll need to add a migration path to the iOS app before the Mac build ships. We're aware of App Groups and have read App Groups: macOS vs iOS: Working Towards Harmony. What this post doesn't cover is whether an app group is an appropriate bridge for this scenario. If not, what would you recommend instead?

Hello, I have an internal TestFlight build for my app PewPewApp (Apple ID 6760741808). The build is processed, assigned to an internal group, and the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. However, installation from TestFlight fails with: “The requested app is not available or doesn’t exist.” Could you please check whether there is an account-level or backend TestFlight distribution issue affecting this app/build? Thank you.

When I submit the app to TestFlight beta review I get the error show on UI. (I filled all filed info in Beta Infomation) There was an error processing your request. Please try again later I was inspected Safari to see the detailed error and I got the below error. Failed to load resource: the server responded with a status of 422 () and the detailed javascript error componentStack: undefined errorCode: undefined message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" stackTrace: "status code: 422 --- api correlation key: NZEKCTWMNANXDZVTRD3V4GNE3U" Anyone can tell me the problem and how to fix it. Many Thanks.

Our company enrolled in the Apple Developer Program as an Organization. Apple successfully created our D-U-N-S Number, but our enrollment has remained "Being Processed" for an extended period. I have contacted Apple Developer Support three times regarding this issue. Each time, I received only the automated acknowledgment email, and the same Case ID was referenced every time. However, I have never received any response from a support representative. At this point, our company is completely blocked from publishing our iOS application. Has anyone experienced the same issue recently? If so, how was it resolved? If an Apple Developer Support representative sees this post, I would sincerely appreciate it if you could review my case or advise on the next steps. Thank you.

Hi, I'm unable to install my app through TestFlight. When I tap Install, TestFlight immediately shows: "The requested app is not available or doesn't exist." What I've verified: Build upload succeeds. Build processing completes successfully. Build is assigned to my internal testing group. Bundle ID is correct. Same Apple ID is used for App Store Connect and TestFlight. The app installs and runs correctly on the same iPhone when installed directly from Xcode. I've already tried: Uploading multiple new builds. Removing and reinstalling TestFlight. Restarting the device. The issue only occurs when installing through TestFlight. Has anyone experienced this recently? Is there anything else I should check? Thanks!

Hello, I'm facing a TestFlight issue that started some time after renewing my Apple Developer Program membership. Issue: Builds upload and process successfully in App Store Connect. Internal testers cannot install any build. TestFlight shows: "The requested app is not available or doesn't exist." Submitting a build for external testing always fails with: "There was an error processing your request." This is happening with every new build and has been occurring for over a last two week. The app had been distributed through TestFlight successfully before this issue started.

NB Dev Support ticket has been open for 9 days 102922985821 We are experiencing significant roadblock as macOS app are stuck 'Processing' after uploading. Current 10 days stuck. It's now affecting our release roadmap, and this is even before we have to wait for the usual extended TestFlight and Production review times that exist for macOS (compared to iOS). The .pkg app is uploaded via Transporter. Transporter reports it has uploaded ok, but in App Store Connect shows it is stuck 'Processing'. Subsequent upload has the same effect. Two previous builds for this build number were rejected (Invalid Binary = signing) but have been fixed - we shouldn't have to bump the build number to free the slot to try again... Note there were a flurry of these issues in Jan 2026, but also at least one other ticket now: https://developer.apple.com/forums/thread/818208 Anyone else seeing this, or been able to resolve? Cheers!

I know that using a mouse to control an iPhone simulator on macOS allows me to swipe down from the top right corner to open the Control Center, but why can't I swipe down from the top left corner to open the Notification Center? Am I doing something wrong, or does iOS disable mouse access to the Notification Center on macOS? Also, it seems that you can't use a mouse or gestures to open the Notification Center or Control Center in iPhone Mirroring at all. I saw that Accessibility has a feature to open the Notification Center or Control Center with the keyboard, but it doesn't work in my tests on macOS. I have an application feature that needs to check the effect of the media playback cards in the Notification Center, but I can't check it at all. Every time I compile to a real device and test manually. Is there any way to reliably trigger the Notification Center and Control Center on macOS? Otherwise, testing on a real device every time is too cumbersome, and I can't automate the testing at all!

Account-level TestFlight failure after app transfer. All apps (including brand-new, non-transferred app) fail with "The requested app is not available or doesn't exist" (Team JYHS43K259) Since receiving several apps via App Transfer, no app on my team can be installed through TestFlight. Every install attempt fails with: "Could not install [App Name]. The requested app is not available or doesn't exist." Critically, this affects not only the transferred apps but also a brand-new app created directly on this account with no transfer history. This indicates an account-level distribution problem rather than an app-record issue. Account details Account holder: BULENT TEKBAS Team ID: JYHS43K259 Account type: Individual Support case: 102936985904 — open for 5+ business days with no substantive response Affected apps Uyku Sesleri — Bundle ID: com.octo8.uykusesleri — Apple ID: 6759616379 — transferred to this account on June 13, 2026 Bekçilik Sınavı 2026 — Bundle ID: com.alhn7.bekciliksinavi2026 — Apple ID: 6756800265 — transferred July 1, 2026 VitaminD — Bundle ID: com.octo8.vitamind — Apple ID: 6768099487 — transferred July 9, 2026 Arete — Bundle ID: com.octo8.arete — created natively on this account, never transferred, currently TestFlight-only All four apps exhibit the identical install failure. Symptoms Builds upload, process, and reach "Testing" status normally Builds are visible in the TestFlight app with an Install button Tapping Install immediately fails with "The requested app is not available or doesn't exist" Reproduced on iPhone 16 Pro running iOS 26 and iOS 27 Internal testing, external testing, and public links all fail identically Already verified / attempted Paid and Free Applications Agreements: Active; banking and tax information complete Pricing and Availability: available in all territories; no app is Removed from Sale Created new versions in "Prepare for Submission" state App Privacy details published; export compliance resolved on all builds Trader status / DSA declaration completed Deleted and reinstalled TestFlight; signed out of Media & Purchases; restarted device; signed back in; accepted freshly generated invitations Removed all testers and re-invited them; generated new public links Uploaded multiple new builds with incremented build numbers — all process successfully, all fail to install Why this appears to be account-level Arete (com.octo8.arete) is a new app with a new bundle ID, created, signed, and uploaded entirely under Team JYHS43K259, with no connection to any previous team. It fails identically to the three transferred apps. The only common factor across all four apps is the team itself. Request Could someone from Apple please check whether Team JYHS43K259 is in a held or degraded distribution state following the recent app transfers? Case 102936985904 has been unanswered for over five business days, and this is blocking updates to live apps with active subscribers. I can provide sysdiagnose logs, build IDs, or any additional information immediately.

Hi everyone, I'm looking to see if there is a current queue backlog or if an Apple representative might be able to take a look at our status. Our game's very first external TestFlight build has been sitting in "Waiting for Review" with no movement. App Name: Pippin Plaza - 4 Player Co-op App ID: 6787434739 Version & Build: Version 1.0 (Build 2) Submitted: July 15, 2026 Current Status: Waiting for Review The Test Information metadata, contact details, and App Tracking Transparency prompts are fully detailed and filled out. Are any other indie developers experiencing multi-day TestFlight delays this week, or is this standard for a first-time external version review right now? Any insight or visibility from Apple would be deeply appreciated!

My app has been released successfully to App Store, and I still need more tests with the TestFlight version. But when installing this app from Test Flight I got the error "The requested app is not available or doesn't exist". Also, when I choose "submit for review" to get a public shareable link I got the error "There was an error processing your request. Please try again later". I want to know exactly what error is happening with my app.

Hello everyone! Having a bit of an issue with Testflight. I can upload my builds perfectly fine. I'll get an email saying the app is available for testing. I'll go into Testflight. All my apps show up. There's an install button right by the app. I'll click install, and a dialog box pops up saying that the app couldn't install. "The requested app is not available or doesn't exist." Well, the app is obviously there, so it does exist. So I really don't know what the issue is. I really need this resolved! Thanks!

Hi everyone, I submitted my app's first build for external TestFlight testing and it has been sitting in "Waiting for Review" for more than 48 hours. There are no messages in the App Review section and no rejection, the status is simply "Waiting for Review", so it doesn't look blocked, just not picked up yet. A few questions for those who've been through this: For a FIRST external Beta App Review, how long did yours actually take? Is 48h+ normal these days, or is something wrong? Does the first external review really take much longer than later builds? I've read that once your app clears Beta App Review the first time, subsequent builds are approved almost instantly, can anyone confirm from experience? Has contacting App Review support ever actually sped this up for you, or is it just a matter of waiting it out? Any real-world experiences or rough timelines would help me set expectations. Thanks a lot!

I'm getting error when I'm trying to install TestFlight I'm getting the requested app does not exist or not available error, TestFlight delivery was successful and also setup is correct, our app is still in development and we have release any version on app store yet, we are testing via TestFlight, please help to resolve this issue. I have raised many support requests as well but not getting any response

I was previously able to test my app on Xcode 27 / iOS 27 by setting the Xcode Version to "Latest beta or release". I needed this to test PrivateCloudCompute on my apps in TestFlight. As of a few days ago this stopped working and only shows the stable 26 release, which removes PCC and my ability to test it. Am I doing something wrong? I didnt change any settings, I just noticed PCC wasnt working, checked the workflow and noticed that it no longer shows Xcode 27.

My app has been sitting in Beta App Review for an extended period with no update. I opened a support ticket through the developer contact form and never received a response. I also called Apple Support through the consumer line, but they weren't able to access developer/App Review case details and redirected me back to the same channel that already isn't responding. Has anyone else run into a review request that stalls with no reviewer feedback and no response to a filed ticket? Looking for: Any way to escalate beyond the standard contact form Typical wait times others have seen for a stuck Beta App Review before it's worth re-submitting a new build vs. waiting Whether there's a different queue/contact specifically for TestFlight (as opposed to full App Store review) Appreciate any pointers.

Hello. I have a problem with the FoundationModels adapter and the Apple-hosted managed asset pack via TestFlight. I have created an adapter that works fine locally by creating a model via (fileURL: URL) on a real device, but I cannot create a model using background assets by downloading the adapter via TestFlight. Every time I try to get an adapter, the creation of the adapter is interrupted by the compatibleAdapterNotFound error. The aar. archive i created using a special command - xcrun ba-package foundation-models package --adapter-path aurelius1.fmadapter --asset-pack-id fmadapter-aurelius1-9799725 --output-path ./aurelius1.aar --platforms iOS --on-demand\ after that, I replaced "OnDemand": null with "OnDemand": {} in the manifest so that the Transporter could send my archive to the App Store Connect. I followed all the recommendations in this topic - https://origin-devforums.apple.com/forums/thread/823148 ...but unfortunately unsuccessfully I would appreciate any help in solving this problem. here is the code that I use in my app -