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.

Hi, Recently I encountered troubles uploading a binary with temporary-exception.audio-unit-host entitlement using Transporter. I would love to make use of in my application and distribute in the AppStore. What is necessary to do so? regards, Joël

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

Hi everyone, I currently have two apps stuck in TestFlight beta review for over 30 days without any progress: App ID: 6749024874 — Case ID: 102673603146 App ID: 6749025418 — Case ID: 102673604516 I contacted Apple Support, but they told me this situation is “normal.” From my experience, TestFlight reviews usually take a day or two, sometimes up to a week, but not this long. Has anyone else experienced such long delays with TestFlight beta reviews? Is there anything I should do (cancel and resubmit, escalate further, or just wait)? I would also like to request support from the App Review team to look into these case IDs and provide clarification. Thank you.

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?

Hi anyone facing the same problem as mine when I try to replace my current app has downloaded from app store then reinstall in testflight my UserDefault got wiped even bundleID in app store and testflight are the same.

I archived the app via Xcode for App Store Connect. When I upload this build to iPhone via TestFlight everything works fine, but when I send it to Apple they get a black screen. Please tell me what the problem is

I am a recently joined developer. However, I have 5 app builds, and 3 are in live in the App Store. I recently updated from iPhone 13 mini to iPhone 16e. I am logged into iCloud with my personal Apple ID, but in media & purchases, I am logged in with my Apple dev ID (email has my company domain). For some reason, only my oldest app build is visible in testflight on my iPhone. Logging in on MacBook, I see all 5 apps and current builds. Under testflight tab there, the correct group with my email (same as developer account ID) is listed as invited. Yet, none are visible in my iPhone testflight. Clicking on the invite email gives "Couldn't Load App This invitation cannot be accepted because your Apple Account, (redacted) has already been associated to this app." Does anyone, please, have any advice???

With no explanation, all of my app builds in Testflight have vanished. There is no record of them in the Testflight mobile app. I am very confused and frustrated as I have 4 or 5 apps in the pipeline that are now unable to test. What happened here?

Hi, I have a .NET MAUI app running on .NET 9. When I test locally in debug or release mode it works perfectly fine, but when testing from TestFlight it crashes almost immediately every time. I have sent the crash report to TestFlight and produced the symbolicated.crash file (attached), but I'm not sure it's helpful for understanding how to fix the issue. If anyone can help me understand what the issue might be and any possible fixes it'd be very much appreciated. I'm developing using Visual Studio 2022 paired to my Mac. I have distributed previously without issue, but now can't seem to, even after reverting recent code. net9.0-ios 15.0 symbolicated.crash

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?

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!

Hi, I am facing a very weird issue where I am unable to download our own application from TestFlight for testing. This issue only happens for one of our applications; we are able to download our other applications without any issues. Furthermore, this only happens on one of our MacBooks; the game downloads fine on our other MacBook (macOS 15) and can run our application. When running the console, I noticed this error being thrown when the TestFlight fails the download: I have tried reinstalling TestFlight, clearing all instances of our application as what Finder can find, restarting the MacBook but nothing worked. Is there anyone that faced this similar issue, or any Apple staff that could help with this? OS version: macOS Tahoe (26 Beta) latest TestFlight was able to download on this version previously, until one day it couldn't (and not sure why), tried downloading latest version but did not solve the issue. Note: We noticed that we are unable to install our own application from the Appstore as well, on this MacBook that has the TestFlight issue.

Hi Have uploaded the build version and status now is approved, but this build is not showing under testflight previous builds, not able to install this version. Also when adding independent tester, error occured showing like bolow, retry not work. Anyone facing this problem ?

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.

I’m seeing an issue with subscriptions in TestFlight builds on iOS 26. Running from Xcode works as expected, and the App Store build looks fine. But when I install the same build via TestFlight, transaction.subscriptionStatus is nil. The identical binary behaves correctly on an iOS 18 device. Is this expected behavior on iOS 26 TestFlight, or am I missing something? Thanks!

https://testflight.apple.com/join/3WFJJ4YQ

Good afternoon, all! I was wondering if there was a timeline for when the App Store and/or TestFlight will drop support for Swift 5? I know Swift 6 was released last year and historically App Store requires a certain SDK minimum for upload. I was wondering if any SDK update was on the docket that would effectively force applications onto Swift 6? Looking at past releases, I had estimated mid to late 2026, but I wanted to confirm? Swift 4 Released September 2017 Became the default SDK in Xcode 9 Strongly "encouraged" via the iOS 12 SDK in late 2018 Essentially "required" by early 2019 Swift 5 Released March 2019 Became the default SDK in Xcode 10.2 Strongly "encouraged" via the iOS 12.1 SDK in early 2019 Essentially "required" by late 2020 Swift 6 Released June 2024 Became the default SDK in Xcode 16 Strongly "encouraged" via the iOS 18 SDK in April 2025 **Essentially "required" by mide-late 2026 ?? ** Thank you in advance!

I have the following technical scenario: I need to implement the “Update Now” alert flow that forces the user to download the latest version from the App Store before continuing to use the application. Conditions and limitations: I have no access to the frontend code, I can only make changes in the backend. The current version of the app was not designed to receive or process a signal from the backend indicating that the update alert should be displayed. The current frontend is connected to a different backend(PHP) than the one that will be used for the new app version, so it is not possible to implement this logic on the client side for older versions. Goal: To find out if there is any method, configuration, or API (for example, in App Store Connect or through some distribution mechanism) that allows forcing the mandatory update alert without modifying the current binary or frontend, only through backend responses or settings. Has anyone implemented this type of control, or does Apple provide any tool to achieve this? Thanks.

Hello Apple Developer Support / Community, I’m currently experiencing an unusually long delay with the review process for my app. I submitted a new build several days ago, but the status has remained "Waiting for Review" with no progress or updates. App ID: 6670308720 Normally, my TestFlight or App Store submissions are reviewed within 24–48 hours. This time, however, no builds are moving forward, and it’s causing concern. I'm wondering: Is there a known issue with the review system lately? Should I remove the current build and submit a new one to reset the review queue? Has anyone else experienced the same issue recently? Thank you!

Hi everyone, Lately, I’ve noticed that TestFlight beta reviews are taking much longer than usual. In the past, my updates were typically reviewed and approved within 24 hours. However, recently none of my builds have been approved, even after several days of waiting. My app ID is: 6670308720 Is anyone else experiencing similar delays? I'm wondering if there's an issue with my account or if Apple has changed the review process timelines.