I've reached maximum number of testers for my app. That's why I've deleted all testers from TestFlight to clean testers list and invite new and old testers again by public link. But deleted testers are still count in "All testers", but in "Deleted testers" filter. And the error "You’ve added the maximum number of external testers for this app" still occurs. Is this how it's supposed to work or is this a bug?

Hi, Got this message when i try to test new version of my App with testFlight: "The requested app is not available or does not exist." Look on many post, but app is active on Store, last version is 2 month ago. Any idea ? Regards.

Hello, I'm receiving error StoreKit: Failed to get response from platform. I have user in SandBox, that user is logged on physical device, I have correct bundleID. Product is Approved I tested via StoreKit configuration file and that worked just fine. also tried to build app and push to test flight, this way same error. Any recommendations what I can check ? Thanks

I cannot add myself as a TestFlight user to my own app. When I open the invite link on my device, or manually enter the redeem code on device (obtained from opening the invite link on macOS), I get "This invitation has been revoked or is invalid". I've tried going to App Store Connect and removing myself from both the testing group and the list of 'All testers', both to no avail. Apple folks: this is not user error and you must have thousands of bug reports on this by now. Why don't you prioritize a fix for this incredibly annoying issue?

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'm repeatedly hitting an issue when deploying Xcode Cloud builds to macOS from TestFlight. Once the build appears in TestFlight I hit the "Install" or "Update" button in TestFlight and after a couple of seconds of spinning-wheel the button goes back to it's original state and the app fails to install. There's no error pop-up but I've noticed an Error Domain=ASDErrorDomain Code=710 "Invalid hash 'xxx' expected 'yyy'" error in console each time it happens. My project needs to deploy 2 different macOS/Catalyst apps (actually they are 2 different targets in the same project) and it seems completely random as to which will actually successfully install on which machine. For my last build, one of the 2 binaries was failing to install on a Mac Studio on 15.5, but the other was fine. All were fine on 3 other machines I tried. For my latest build, both binaries are fine on the Mac Studio but both now fail to install on an M2 Air on macOS 26 beta 2. I'm now extremely nervous about deploying to my TestFlight beta group in case users have similar problems.

Not able to enable external testing of my app due to phone number validation. The error reports "Make sure the contact phone number only contains numbers and try again.". Attached is a dummy phone number with the same validation result.

Hei! I'm currently running into an issue that I cannot create App Clip Invocations for a build in Appstore Connect. Tested with Safari, Chrome and Firefox. Also with a Windows machine. I select the build from TestFlight view I click "Add App Clip Invocation" I fill the data in the modal I click "Add" Nothing happens and I don't see any errors in the logs in developer tools with the browsers.

Hi everyone, I’m having trouble distributing my app via TestFlight. I created the app completely from scratch — new bundle ID, new build number, fresh provisioning profile, and certificates. Everything looks correctly set up in App Store Connect, and the build is marked as ready for testing. However, when I send the TestFlight link to testers, they get a message saying the app is "unavailable" or "not found." I’ve double-checked all settings, and I can’t figure out what I’m missing. Has anyone experienced this before or have any suggestions on how to fix it? Any help is appreciated!

Although the application functions correctly when deployed locally to a physical iPhone using Flutter (direct debug/development build via Xcode), we are encountering the following issues only within App Store Connect / TestFlight: 1- Internal Testing Issue: After completing all required steps in App Store Connect and adding internal testers, testers are unable to install the app. TestFlight displays the error: “Could not install app. The requested app is not available or doesn’t exist.” 2- External Testing Issue: When attempting to add a processed build to an External Testing group (Public Link), App Store Connect returns the following message: “There was an error processing your request. Please try again later.” The build has successfully uploaded and processed, and is marked as Ready to Submit in TestFlight. These issues do not occur during direct device deployment and appear to be isolated to TestFlight / App Store Connect. We would appreciate guidance on how to solve this issue which is preventing TestFlight distribution. *Note: we tried multible builds and upgraded the version 4 times, and we signed all agreements.

My developer posted the latest beta release of our app to test flight. When I went to install it on my Mac - the the progress circle gets about 2/3 of the way to completion, then installation stops - and I see the Install button again. Apple M1 / 16GB ram / Sequoia 15.3

We’re seeing a strange issue with our TestFlight setup. We normally have 4 apps available in TestFlight (all of which are also live on the App Store). Today, 3 of them disappeared from TestFlight because their builds were marked as expired. I re-submitted new test flight builds, which made the apps reappear but now when trying to install ANY of our apps, we get an error saying: “The requested app is not available or doesn’t exist.” There are no issues or flags on the TestFlight pages in App Store Connect, all builds are validated, and all apps are still downloadable from the App Store without any problems. Has anyone else experienced this?

Hello, I uploaded my application to TestFlight via Expo (React Native), but I am unable to install it on iOS, nor can I submit it for external testing. Thank you.

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

I am unable to install my app via TestFlight.When I tap Install in TestFlight, I receive the following error message: “Could not install xxx. The requested app is not available or doesn’t exist.” The app is visible in TestFlight, but installation always fails. I would appreciate your help in identifying the cause.

Has anyone seen Managed Background Assets get stuck before any download progress is reported on iPadOS 26.3 / TestFlight? We are using Apple-hosted managed asset packs for a large on-demand model download. The app can resolve the asset pack metadata: we can show the asset pack’s download size in the UI, so AssetPackManager.assetPack(withID:) appears to work. But when we call ensureLocalAvailability(of:), the UI stays at 0% indefinitely. We also do not receive any useful terminal state from statusUpdates(forAssetPackWithID:): no .began, .downloading, .failed, or .finished. The app remains responsive. The issue also appears persistent on the affected device/account. Reinstalling the app does not help, reinstalling TestFlight does not help, logging out and back in does not help, and restarting the device does not help. After each attempt, the app can still resolve the asset pack metadata/download size, but the actual download remains stuck before any progress or failure status is delivered. The suspicious part of the device log is that the managed helper starts normally, fetches/installs the manifest from TestFlight, but repeatedly fails to create its helper directory inside the app container: OurApp Initializing the asset-pack manager… OurApp Creating a proxy object for the helper service… OurApp activating connection ... name=com.apple.backgroundassets.managed.helper.service kernel Sandbox: no system container path found for ID "com.apple.backgroundassets.managed.helper.service" Managed Background Assets Helper Service Starting the Managed Background Assets Helper Service… Managed Background Assets Helper Service Configuring the directory suffix… Managed Background Assets Helper Service The directory suffix was successfully configured. Managed Background Assets Helper Service The extension token "<...>" was consumed. kernel Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] After that, manifest fetching still seems to work: OurApp The asset-pack manager has been initialized. OurApp The system download-manager delegate has been assigned to the download manager. OurApp The app was installed for internal beta testing; checking for updates automatically… OurApp Refreshing the manifest… Managed Background Assets Helper Service The app with the bundle ID "..." is configured to use Apple hosting. Managed Background Assets Helper Service Asking the TestFlight extension via the App Store Daemon for the URL request... Managed Background Assets Helper Service Fetching the download manifest ... from TestFlight… Managed Background Assets Helper Service Installing a manifest at ".../Library/Application Support/.../Manifest.json"... But during/after manifest install, the same mkdir failure appears again: Managed Background Assets Helper Service Installing a manifest at ".../Manifest.json"... Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] kernel duplicate reports for Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service So the behavior seems to be: TestFlight/internal beta install Apple-hosted managed asset pack Manifest fetch succeeds Asset pack metadata resolves, including download size Actual local availability request never starts reporting progress No visible Background Assets failure reaches the app Logs show repeated sandbox file-write-create denial for the Managed Background Assets Helper trying to create /tmp/com.apple.backgroundassets.managed.helper.service inside the app container Reinstalling the app/TestFlight, logging out and back in, and restarting the device do not clear the stuck state On devices with 26.4, the issue doesn’t seem to exist Has anyone else seen this on iOS/iPadOS/macOS versions before 26.4? Is this a known issue in the Managed Background Assets helper/runtime? I noticed 26.4 added more local status APIs for asset packs, so I’m wondering whether this area changed in 26.4. Any hints on whether the sandbox denial is expected/noisy, or whether it could explain ensureLocalAvailability(of:) never progressing, would be appreciated.

Error in TestFlight: “The requested app is not available or does not exist.” This happens on multiple iPhones and Apple IDs. Important: Builds from OTHER Apple Developer accounts install fine on the same devices. We tried new apps, new bundle IDs, new certificates, new provisioning profiles. Internal testing fails. External testing also fails. All Agreements, Tax, Banking, and membership requirements are completed and active. When configuring external testing in App Store Connect, we also get: “There was an error processing your request. Please try again later.” This has been happening for 3 weeks. Has anyone seen an Apple Developer account / TestFlight backend issue like this? Any solution besides contacting Apple Developer Support?

Same scenario described here: https://forums.developer.apple.com/forums/thread/738942 User clicked accept for an internal tester invitation sent to their work apple id on their personal device which was signed in with their personal apple id. This seems to have redeemed the code to the users personal account. However, the user has removed themselves from testing the app and we're trying to get their work apple id registered but the invite code that keeps being sent is coming back saying invalid. Things we've tried: We located the last build the user installed on their device and expired the builds deleted / readded the work apple id to internal testing group It's still sending the same invitation code from TestFlight and saying that the code cannot be redeemed.

Hello, Apple Developer Community! I am attempting to test a user upgrade scenario from an existing monthly subscription to a yearly subscription, applying a Promotional Offer within the sandbox environment. When trying to process the transaction, I consistently receive the following errors from StoreKit: <SKPaymentQueue: 0x...>: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3903 "Unable to Purchase" UserInfo={NSLocalizedFailureReason=Unable to Purchase, client-environment-type=Sandbox, AMSServerErrorCode=3903, storefront-country-code=USA} [...]: Finishing transaction <SKPaymentTransaction: 0x...> with no identifier Additionally, the standard dialog shown to the user displays: Unable to Purchase Contact the developer for more information. [Environment: Sandbox] My Implementation Details: Scenario: The user has an active monthly subscription and attempts to upgrade to a yearly subscription with a Promotional Offer (discount). Signature Generation: I use a custom backend written in Go to generate the signature, nonce, and timestamp. The code follows Apple’s documentation requirements, including proper encoding and formatting. Client (iOS): On the Swift side, I correctly initialize the SKPaymentDiscount and add it to the SKMutablePayment before adding the payment to the queue. The applicationUsername property is used and matches on both server and client sides. What I Have Already Verified and Ruled Out: New Test Accounts: I have created multiple fresh sandbox tester accounts in different regions (USA, Canada, Germany) and used them. Time Synchronization: The time on my server and the test device is synchronized. Parameters: Bundle ID, Product ID, and Offer ID match exactly with the configurations in App Store Connect. App Store Connect Agreements: The Paid Applications Agreement is active. Testing Environment: Testing is conducted on a physical device (iPhone), not a simulator. It seems the issue may not be related to my code but rather a potential glitch within the Apple sandbox environment itself when processing complex upgrade requests with a promotional offer. Has anyone encountered a similar issue when testing Promotional Offers? I would appreciate any help or guidance.

Hi everyone, I’m preparing an updated version of my older game Plum Nut so I can eventually return it to the App Store. I’ve uploaded a new build (1.1 build 8) and it shows up correctly in TestFlight for beta testing. However, when I try to install it on a supported device (iPad Pro 2020, iOS), I get this popup: “Could not install Plum Nut. The requested app is not available or doesn’t exist.” The build is processed and available in TestFlight, but installation always fails with this message. I have several games that install fine on TestFlight. This is the first and only case and time where I have encountered this. Details: Platform: iOS Build: 1.1 (8) TestFlight status: Available for testing Issue first occurred: Nov 18, 2025 I contacted Apple Developer Support, but they directed me to the forums for technical guidance. If anyone has encountered this issue or has suggestions on what might cause it, I would be very grateful for any insight. Thank you! — Rob / Protopop Games