TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.

The new search bar in TestFlight is a welcome addition—thank you! However, apps now appear to be sorted alphabetically instead of by their latest update. This makes it much harder to find newly updated builds, especially when testing many apps (we have >100). Could you please restore sorting by most recently updated, or add an option to choose the sorting method?

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?

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.

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.

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.

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.

A sandboxed Mac app with correct CloudKit entitlements fails to connect to com.apple.cloudd (the CloudKit daemon) when distributed via TestFlight (Mac Team Store Provisioning Profile). The identical binary works correctly when launched from Xcode (Mac Team Provisioning Profile also present). All entitlements are correctly embedded and the App ID is properly configured in Apple Developer Portal. Environment macOS 26.5.1 (25F80) Xcode 26.5 (17F42) SwiftData with NSPersistentCloudKitContainer / ModelConfiguration(cloudKitDatabase: .private(...)) Steps to Reproduce Create a sandboxed Mac app using SwiftData with CloudKit sync Enable iCloud + CloudKit in Signing & Capabilities Archive and distribute to TestFlight (Mac Team Store Provisioning Profile) Install via TestFlight on macOS 26 and launch Check Console for kernel sandbox messages Expected Result CloudKit connects to com.apple.cloudd and syncs data, matching behavior of the iOS version using the same container. Actual Result Console shows repeated kernel sandbox denials followed by CloudKit setup failure: kernel Sandbox: CheatSheet Mac(82347) deny(1) mach-lookup com.apple.cloudd kernel Sandbox: CheatSheet Mac(82347) deny(1) mach-lookup com.apple.duetactivityscheduler CheatSheet Mac CoreData+CloudKit: Failed to set up CloudKit integration for store Error Domain=CKErrorDomain Code=6 "Error connecting to CloudKit daemon." Key Diagnostic Finding When launched from Xcode, taskgated-helper validates both the Mac Team Store Provisioning Profile AND the Mac Team Provisioning Profile, and CloudKit succeeds: cloudd: TCC approved access for container containerID=iCloud.com.michaelendres.CheatSheet:Production When launched from TestFlight, only the Mac Team Store Provisioning Profile is present, and the sandbox denies com.apple.cloudd despite identical entitlements in the binary: codesign -d --entitlements shows: com.apple.developer.icloud-services: [CloudKit] com.apple.developer.icloud-container-identifiers: [iCloud.com.michaelendres.CheatSheet] com.apple.developer.icloud-container-environment: Production com.apple.security.app-sandbox: true Conclusion The Mac Team Store Provisioning Profile on macOS 26 does not appear to grant the sandbox exception for mach-lookup com.apple.cloudd, while the Mac Team Provisioning Profile (development) does. This prevents any Mac App Store / TestFlight app using CloudKit from syncing on macOS 26.

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!

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!

I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?

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.

Anyone is experiencing this issue? Today without any reason we can think of, all of our builds were expired on Testflight. Without knowing what happened, then we tried to add a new build, that it it seems to be in good shape on Testflight, even with the mark green meaning is ready to be tested. Even though, by trying to install the app on iOS using TF, we are getting a message saying "The requested app is not available"

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 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!