Trying to add some release test notes to a TestFlight build - but after clicking the blue save button nothing happens, nothing is saved. I tried with two different browsers and two different Apple accounts, same thing with both. Anybody else experiencing this issue?

Hello, My app (App ID: 1616628950) is already published on the App Store, but recently we’ve been unable to install the TestFlight build for testing. The TestFlight build shows the green “Testing” status, but whenever we try to install it, we get this message: “Could not install / The requested application is not available or does not exist.” The TestFlight version is the same as the one currently live on the App Store, and the App Store version installs without any issue. I wanted to share this here in case someone from the team could check whether the TestFlight build might be stuck or misconfigured on the backend. Thank you very much for your time and help!

I can't accept a TestFlight invitation. I seemed to have gotten myself into some situation that I have been unable to resolve. Here's what I did: Added my work Apple Account to TestFlight. Received an email for TestFlight invitation. Opened link in browser to view invitation code. Entered that code on a device that was signed into a different Apple Account (my personal account on my personal iPhone). The app did install on my personal iPhone, but now I can't accept the invite on my test device, which is signed into the Apple Account that is actually part of the TestFlight group in App Store Connect. I have tried deleting/re-adding/re-inviting my work Apple Account to TestFlight several times. On my personal iPhone, I have tapped on "Stop Testing" in the TestFlight app and deleted the app I installed there. But I still cannot accept the invite on the test device signed into my work account. When I enter the invite code to redeem, it says: This invitation cannot be accepted because your Apple Account, , has already been asso... The full message is actually truncated, so do not know what it says after "asso...". Is there any way to get out of this situation and accept the invite on the test device using my work Apple Account?

Hello, I was just installing an app from TestFlight that has an Essential Asset Pack that's a few GBs in size. It appears the Call To Action inside of TestFlight doesn't take into consideration the Background Asset download status before it changes from Installing to Open. I can't test if this is also the case for apps on the App Store, but I'd expect that it is.

今天上午开始TestFlight一直都是processing。

Hi everyone, I'm experiencing an issue with TestFlight where internal testers are not receiving build invitations, even though the builds have successfully completed processing in App Store Connect. Builds Status: • Multiple builds (Build 10, 11, 12) show "Ready to Submit" status in App Store Connect • Build 9 is in "Waiting for Review" status • All builds show "2 Invites" sent • However, the new builds (9, 10, 11, 12) are not appearing in TestFlight for the internal testing group Internal Testing Group: • Group name: "Test" (Internal Group) • 2 Testers configured • 7 Builds total in the group • The group shows builds 1.0 (2) through 1.0 (8) as "Testing" status • New builds (9, 10, 11, 12) are missing from TestFlight What I've Tried: Manually adding the internal group to the new builds using the "Add Group" dialog(the Add button is inactive) The system shows "2 Invites" sent in App Store Connect Checked TestFlight app on testers' devices - no new builds visible Waited more than 1 hour after builds completed processing Expected Behavior When adding an internal testing group to a build in App Store Connect, testers should: Receive push notifications about the new build See the new build available in their TestFlight app Be able to install and test the build immediately Actual Behavior • App Store Connect shows invitations were sent (2 invites) • TestFlight does not show the new builds (9, 10, 11, 12) • Internal testers have not received any notifications • Only older builds (2-8) are visible in TestFlight Additional Context • This issue started occurring today (January 15, 2026) • Yesterday, I experienced extended build processing times (builds stuck in "Processing" for several hours), which appears to have been a widespread issue affecting multiple developers • Once processing completed, the builds moved to "Ready to Submit" status normally • The internal testing group worked fine for previous builds (2-8) Questions Has anyone else experienced this issue with TestFlight internal testing today? Is there a known delay between adding a group in App Store Connect and builds appearing in TestFlight? Could this be related to the processing delays that occurred yesterday? Is there a way to manually trigger the invitation/notification system? Any insights or suggestions would be greatly appreciated. This is blocking our internal testing workflow. Thanks in advance!

Hello everyone, I successfully submitted my iOS app build to App Store Connect via EAS(expo.dev). The submission logs confirm successful upload, but the build is not visible in App store connect TestFlight → Builds after several hours. Submission was successful according to logs: "Successfully uploaded package to App Store Connect" and "The app has been submitted successfully." Has anyone experienced a problem with this? Can I get some information? Thank you.

Hi, I’m experiencing unusually long processing times for TestFlight builds in App Store Connect. Details: App version: 1.0.0 Build numbers affected: 49 and 50 Status: “Processing” for 13+ hours Previous build (48) processed successfully the same day (10min) The builds were uploaded successfully, and there are no changes to provisioning profiles or certificates. The only differences between the builds are minor code changes with paywall. Is it normal for TestFlight builds to remain in “Processing” for this long?

I recently submitted an app for external testing via TestFlight, but it has been stuck at the "Waiting for Review" status for several weeks. This delay is blocking our testing process and impacting our development timeline. Could you please look into this issue and provide an update on the review status? Thank you for your support.

For ages, we've been using appStoreReceiptUrl to detect if the app was installed from TestFlight or not, but now that's deprecated. Since we have a strict policy of no warnings on the project, we need to find a way to check if the app was installed from TestFlight or from the App Store. Does anyone know what's the new way to do so? I thought about using MarketplaceKit.AppDistributor.testFlight but to use MarketplaceKit you need to jump through hoops that our app really doesn't need to - we don't distribute outside of the App Store. Any ideas are much appreciated! 🙏

I have an app clip installed via TestFlight. My AASA file is configured correctly (per 'Domain Status' in TestFlight). I want to be able to run the app clip flow (app clip card showing and app clip card launched) by invoking UIApplication.shared.open(url) from a different app, or by pressing the URL from notes app. This doesn't seem to work. The only thing I am able to do is run the flow when scanning a proper QR code after configuring Local Experience with the matching parameters. But as stated above, the flow will not work when invoking the URL from a different app. Is the proper way to fix this is to define an HTML page for that URL path that contain the element with app-clip-bundle-id attribute that will match the Local Experience configuration? Is there another way to make this flow work with TestFlight releases? what are my options?

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.

I have a binary that successfully install & run on my Mac, that is build with codesign and pkgbuild with "Developer ID Application" and "Developer ID Installer" identities. I cannot figure out how to transform this pkg into a distribution package that fits with App Store and TestFlight. Xcode builds it fine and can run it seemingly, but cannot provide the App Store Distribution option in Organizer after creation of Archive. (Only Custom option.) I probably may not be able to specify properly the build Target as Release (don't know where to specify). (pkgbuild ->) productbuild -> Transporter is also an option, but don't know how to properly specify the productbuild --component options... I have a developer program and can generate the Apple developers certificate fine, such as "3rd Party Mac Developer Application/Installer". A pkg codesign'ed by them was rejected by the notarization process. My application is C and can be started again as New project from Xcode as "MacOS Command-Line Tool", so in other words my question can be said as "how can I organize a MacOS Command-line tool to conform as App Store distribution?" I am checking documents but so far cannot get the proper document. Any pointing to a document is appreciated.

I am trying to invite internal testers but Testflight keeps rejecting them from downloading with a pop up that states "The requested app is not available or doesnt exist" it does say on App store connect that it is Complete as far as to begin testing. Any one have any suggestions? I am new at this. Thank you.

I am unable to receive an invite email on my apple account in order to accept and get access to testflight for testing apps

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connect, but internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local build, Release configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins briefly, then fails with the "not available or doesn't exist" error This affects all internal testers on the account, not just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = Manual, CODE_SIGN_IDENTITY = "iPhone Distribution", with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74D, not expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentials, removed stale profiles, and rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006, but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those cases, Apple Support resolved the issue on their end within 48 hours with no action required from the developer. The signing, provisioning, and build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your side, without any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

Hello Apple Developer Support, We are experiencing an issue with TestFlight Internal Testing. Our internal testers can see the app and the assigned build in the TestFlight app, but when they try to install it, the installation fails with the following error: "Could not install [App Name]. The requested app is not available or doesn't exist." This issue happens with Internal Testing, so Beta App Review should not be involved. We have already checked the following: The build was uploaded successfully through Xcode using App Store Connect distribution. The build processing is completed. The build is assigned to the correct Internal Testing group. The testers are added as App Store Connect users and have access to the app. The app appears in TestFlight for the testers. Agreements, Tax, and Banking do not show any pending actions. Export Compliance / Missing Compliance does not show any pending actions. The issue happens on multiple devices. We have tried removing and reinstalling TestFlight, and uploading a new build number, but the issue still occurs. App details: App Name: WearNow AR Try-On Bundle ID: com.yakovchuk.wearnow Apple Developer Team ID: 6G4QX44Y4A Could you please check whether there is an account-level, app-level, or TestFlight backend issue that prevents this build from being installed by internal testers? This looks similar to multiple recent Apple Developer Forums reports where the app is visible in TestFlight, but installation fails with "The requested app is not available or doesn't exist." Thank you.

I have an iOS app build that is being tested. The user has provided feedback and screenshots that I can see in Connect. But I cannot download the zip file of the screenshot and feedback information. There are 3 screenshots. Each time I try it just times out. I have tried on a couple of different computers with the same result. Can you help please? Thanks

Hello everyone I'm currently experiencing an error when submitting a public link for internal downloads. When I submit and review, it says: "There was an error processing your request. Please try again later." I've reported this to the support team but haven't received a response yet. I would be very grateful if the technical team on this forum could help me. Case ID: 102861441465

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