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 channelyou can share your TestFlight Public Links with the developer communityto gather valuable feedback on crucial elementslike technical implementationuser experiencedesignand more. To maximize the benefits of posting TestFlight Public Links in the Developer Forumshere are some best practices to keep in mind: Provide details: Give comprehensive information about your applike new features and test casesand note specific areas where you seek feedback. The more detailed your post isthe 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.

Hello, My app was rejected on iPad (iPad Air 11-inch M3iPadOS 26.2.1) with two related issues: Guideline 2.1 – Performance – App Completeness “The app exhibited one or more bugs that would negatively impact users. Bug description: the premium subscription cannot be loaded properly.” Guideline 3.1.2 – Business – Payments – Subscriptions “The submission did not include all the required information for apps offering auto-renewable subscriptions.” I am using StoreKit 2 with SubscriptionStoreView to present the auto-renewable subscription. During development: Subscriptions load correctly in the simulator (sandbox). On real devicesI test without a local StoreKit configuration file to fetch products from App Store Connect. The subscription UI (titledurationprice) displays correctly when products are returned. At the time of reviewthe Paid Apps Agreement was not active. I suspect this may have caused the subscription products to fail loading on the review device. Since then: Paid Apps Agreement is now Active. SubscriptionStoreView should automatically show required metadata. Because the subscription failed to load on iPad during reviewthe required information (titlepriceduration) was not visiblewhich likely triggered the 3.1.2 rejection. Additionallyin TestFlight I sometimes see inconsistent behavior where the app appears but cannot be installed (“App Not Available”). Alsomy app was rejectedbut the subscription is still waiting for review. I would really appreciate guidance on the following: Am I potentially missing any required configuration that could prevent products from loading in production? Is there any propagation delay after activating the Paid Apps Agreement that could affect product availability? If I am overlooking something in configuration or testingplease let me know what I should specifically verify before resubmitting. Thank you very much for your help.

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.

I have a tester who switched phones a few months back. Crucially he no longer has access to the old phone. On his new phone when I send him a test flight invite to his apple account123@examplehe receives it but it fails to work when he clicks the link. He is getting the following message. The Apple account (123@example) you're currently signed in with does not match the one (456@example) associated with this invitation. He has no idea what email 456 is. Since his old phone was a hand me downI'm assuming it's someone else's email entirely. I'm trying to figure out how we clear this association out. I tried deleting his app store connect for my app and reinviting him all the way from the beginning. This did not work. As a stopgap I'm giving him a public link under an external testing group but I'd really like to not have to do that. Anyone have any ideas how we can fix this so I can shift him back to the Internal testing group?

One of our apps (built with Xcode 26.1.1 and distributed via TestFlight) crashes upon launch on iOS 17 with Exception Type: EXC_BAD_ACCESS (SIGKILL) and Termination Reason: CODESIGNING 2 Invalid Page. I have never seen this before. Any pointers? On iOS 18 & 26 this does not happen btw.

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-sensitiveas I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

In Xcodeunder Signing & Capabilities (Release) for our bundle ID the selected provisioning profile does include the entitlement: com.apple.developer.payment-pass-provisioning Howeverwhen we upload a new build to TestFlightthe Build Metadata → Entitlements section for the same bundle ID does not include com.apple.developer.payment-pass-provisioning. Because of thisPKAddPaymentPassViewController does not open in TestFlight builds. This suggests that while the entitlement is enabled for the App ID and visible in Xcodeit may not yet be propagated to App Store Connect’s signing service for TestFlight/App Store builds. Please Note: The Wallet Entitlements team had confirmed that they had granted entitlements for our team and the apple IDs Xcode : 26.0.1 Profile being used: Distribution Profile

I uploaded a build to testflight and released it to Internal testershowever when the testers tried downloading the app a alert dialog shows the following: Could not install [App] The requested app is not available or doesn't exist. Also tried to submit it via external testers but getting another error.

We submitted a build to testflight and received a confirmation email it was successfully uploaded. When we open testflight on our iPhone's (X6s) we get a message of "Could not install appname" "The requested app is not available or does not exist" Where appname is the name of the app. Its very confusing because I can see the build listed in testflight on my mobile device and can view it in iTunes connect. I also can't install prior builds that had worked successfully when I try.

My iOS App testflight builds are stuck in Processing for hours. Usually takes 5 mins. Anyone else having this issue? Submitted a Feedback Assistant report.

Hello everyone, I’m reaching out from the music publishing side and would appreciate guidance from developers or anyone familiar with TestFlight governance. We’ve identified an app that has been distributed via TestFlight for an extended period (regular renewalsupdatesand new TestFlight builds). The app’s core functionality involves publishing copyrighted musical works (sheet music)without authorization from the authors or rightsholders. We have attempted to contact the developer using the contact details available through the TestFlight listing and associated project information. To datewe have received no responseand the TestFlight distribution continues. From our perspectivethe developer appears to rely on TestFlight to keep the app off the App Storewhere standard copyright enforcement mechanisms would normally apply. My questions are: Does Apple consider long-termcontinuously renewed TestFlight distribution to be a form of public distribution? Is there a mechanism within the Apple ecosystem to address repeated copyright infringement occurring specifically via TestFlight? From a developer-policy perspectivehow does Apple Inc. typically handle cases where TestFlight is used to bypass compliance obligations rather than for genuine beta testing? I’m not looking for legal advice here — just insight into how Apple and the developer community view and handle this type of situation. Thanks in advance for any guidance or experience you can share.

i need a testflight invitation codeis it possible? i dont really know about the developer e-mail. could you send me a testflight code? here is my email: ******** [Personal Information Edited by Moderator]

Ever since I have upgraded to iOS 26 (at leastI THINK this was when it started) I have been seeing an email account on Testflight purchase flows that is NOT mine. I have never seen this email in my lifeand have not used it during the 10+ years I have been a developer. I do not know how to make this use my Apple ID I am signed into on my device. Howeverlocally signed builds from Xcode still work ok. But I need Testflight builds to work as well. How do I force this account to change?

Environment OS: iOS 26.2 (Beta/Release) Framework: StoreKit 1 (or StoreKit 2) Environment: TestFlight / Sandbox Device: [Insert your device modele.g.iPhone 15 Pro] Description I am encountering a persistent issue where SKPaymentQueue.default().finishTransaction(transaction) does not successfully remove the transaction from the queue. Every time a new purchase is initiatedthe observer triggers an immediate update with the previous transaction's ID (Transaction ID). The system then displays a system alert stating: "You've already purchased this In-App Purchase. It will be restored for free." Even after explicitly calling finishTransactionthe same transaction reappears in the updatedTransactions array upon the next app launch or purchase attempt. Steps to Reproduce Add a transaction observer in didFinishLaunchingWithOptions. Initiate an In-App Purchase in TestFlight. Upon success (.purchased)call SKPaymentQueue.default().finishTransaction(transaction). Attempt to buy the same non-consumable item (or any item) again. Result: The previous transaction is pushed againand the queue never clears. What I’ve Tried Ensured finishTransaction is called on the main thread. Verified that the observer is added at app launch. Manually iterating through SKPaymentQueue.default().transactions and finishing all entries. Signed out of the Sandbox account and used a completely new test account. Deleted and reinstalled the App via TestFlight.

When adding new TestFlight usersthey are not receiving the email invite. I have had them check junk mail and/or other filtering software. Is anyone experiencing the same thing?

Hi, Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know whyhere's an example: Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS). I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols filebut they are unable to work with it. I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?

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 appor 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 abovethe 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'm sure I've probably missed a checkbox somewhere.. I have a mulitiplatform appwhen building from Xcodeand not using the testing configboth iOS and macOS show the correct App Store currency.. When I distribute a build through TestFlightmy Mac version shows a different country/currency price (the US one). I can't find anywhere to change this. My Mac is signed into the same sandbox account as my iOS device. Can anyone help?

My app has in app purchase for subscriptionsavailable in many countries. When using Sandbox App Store accounts on TestFlight with a locale different from my own in the iOS 26 RCI'm getting incorrect currency coming back from Product.products(for: identifiers)and so my app displays the wrong price for the locale. Howeverthe actual Apple Pay buy sheet shows the proper currency symbol and currency amount. This did not happen on prior versions of iOS. Is anyone else experiencing this?

Hello, I’d like to share an issue we recently experienced with TestFlight and ask whether this behavior is expected. Environment App version string: 1.0.0 Multiple builds uploaded via CI/CD Both external TestFlight testing and internal CI builds exist Testers had automatic updates enabled in TestFlight What happened We uploaded build 1.0.0 (2601161653) and assigned it to an external TestFlight group. Testers installed this build and were testing normally. Laterwe uploaded a newer build 1.0.0 (5) and reassigned the same external testers to this build. Testers successfully updated to 1.0.0 (5) and continued testing. After some time (without any manual action from testers)testers received a system notification saying that: “The App has been updated. Version 1.0.0 (2601161653) was automatically downloaded and installed.” When opening TestFlightthe app showed 1.0.0 (5) again as available for updatemeaning the device had already been rolled back to 1.0.0 (2601161653). Additional context There are many archived builds in App Store Connect due to CI/CD testing. Some CI builds share the same version string but differ only in build number. External test groups were only explicitly assigned to build 1.0.0 (5) at the time of the rollback. Build 2601161653 did not have any external test group assigned at that moment. No App Store release or metadata changes occurred during this time. Questions If a tester’s currently installed build becomes temporarily unavailable (e.g. due to eligibilityinternal status changesor TestFlight processing), does TestFlight automatically fall back to a previously approved build? Is this automatic rollback behavior an intended part of TestFlight’s build availability logicespecially when multiple builds with the same version string exist? Can frequent CI/CD uploads (without consistent external group assignment) influence which build TestFlight considers “eligible” or “latest” for testers? Summary From our observationit appears that when the currently tested build temporarily lost eligibilityTestFlight automatically installed a previous build that was still considered availableeven though a newer build existed. We’d appreciate any clarification on whether this behavior is expected or if there are best practices to avoid this situation when using CI/CD with TestFlight. Thank you.

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 buildsneither 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 thisinstallation 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 contactedbut 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 onceor an install failure after replacing expired builds