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.

After creating a new weekly subscription option, I get inconsistent results for subscriptionPeriod. In local testing with a synced or a un-synced StoreKit file I am getting unit == .week (as expected) whereas in TestFlight I am getting unit == .day. This makes unit.localizedDescriptionsomewhat unusable in the paywall. Am I missing something? Or is this bug or a limitation of StoreKit and/or TestFlight and/or newly created subscription options? Affected code (in a custom SubscriptionStoreControlStyle): private func priceDisplay(for pickerOption: Configuration.PickerOption) -> String { var result = "" if pickerOption.introductoryOffer != nil { result += NSLocalizedString("then", comment: "") + " " } result += pickerOption.displayPrice if let unit = pickerOption.subscriptionPeriod?.unit { result += " / " + unit.localizedDescription } return result } private func percentageSaved(for pickerOption: Configuration.PickerOption, allOptions: [Product]) -> Int? { guard let subscriptionPeriod = pickerOption.subscriptionPeriod, subscriptionPeriod != .weekly else { return nil } let weeklyOption = allOptions.first { otherOption in otherOption.subscription?.subscriptionPeriod == .weekly } guard let weeklyOption, weeklyOption.price > 0 else { return nil } let percentageSaved = 100 - (pickerOption.price / (weeklyOption.price * 52)) * 100 return Int((percentageSaved as NSNumber).doubleValue) }

I’m looking for iOS and Apple Watch users to help beta test ChoreFit, a fitness app that transforms everyday chores into measurable workouts using NEAT (Non-Exercise Activity Thermogenesis) science. What it does: • Tracks chores like vacuuming, mopping, and laundry as real workouts • Syncs with Apple Health for steps, heart rate, and calories • Lets you start or pause chores right from your Apple Watch • Adjusts effort based on body weight and optional weighted vests What I need from testers: • Install via TestFlight (link provided once approved) • Use the app during normal household tasks • Share feedback on usability, Apple Watch sync, and calorie accuracy If you’re interested in movement tracking, fitness analytics, or wearable integration, I’d love your help validating and refining this app before public release.

Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning "ITMS-90035: Invalid Signature" TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. The thing is the archives which are not intended for testflight not App Store connect are not failing. I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) : even though certificats seems ok, in Xcode I see a dev certificate in the managed release and if I try to force a distribution certificate in the build I then get the following warning It looks like my managed profile is not behaving properly, like not embedding a distribution certificate. I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name. Anyone has any idea on what is causing those build fails on the archive?

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.

My archived xcode builds show that they have been successfully uploaded to testflight but once in the appstore they do not appear. Is there anyone else with the same problem?

Having been forced to use TestFlight for app distribution (Since Apple changed the policy) bug fixes are taking way too long to go through review. Users have issues, bug fixed in 10 minutes, new release takes 2 days to be reviewed. There has got to be a better way.

Beta reviews have historically taken only a few minutes. Ours has been in review for a day at this point. The Production build is already approved, but our Beta testers still don't have access. Is there anything we can do?

Hi, I run a midsize business. Apple recommends for company owned devices and for other reasons to use Apple Business managed Apple IDs for the employees. After that, you have to use a MDM System for e.g. deploying apps and licenses. Testflight is an app that can be deployed too. But....Testflight can not more than to say "Hello" on a managed device. The use of Testflight and to test our developed apps is not possible with a managed ID. Can anyone explain to me this thinking or what is recommended than. Setting up a private Apple ID for that purpose...which on the other hand, Apple do not want or does not recommend.

Hi, I have deployed my app on Test Flight, I have two subscriptions, monthly and yearly. User can have one of them at a time and upgrade, downgrade to the other. Upgrade, downgrade, cancel from the Apple Settings worked fine in the sandbox environment when testing locally. Now when I have deployed the app on TestFlight, I was able to purchase the subscription successfully from my app. Now when I want to cancel my subscription from the Apple Settings it gives me the following error after confirming cancellation, 'Your request is temporarily unable to be processed. Please try again later.' Also the other subscription offer (yearly) is also not shown to which I could upgrade, even though in the sandbox I was able to upgrade downgrade from the settings. Another thing I have noticed is that the app Icon or name is not shown anywhere in settings with the subscription. Instead of app icon only empty square is shown. Even though app icon shows fine everywhere else. Can someone please help me figure out this issue?

The issue arises only when the .ipa is uploaded to App Store Connect via Xcode. When attempting to download the app through TestFlight, it crashes. This behaviour is isolated to TestFlight and does not occur in any other environment. To clarify the issue: the build is successfully running in Xcode across all iOS devices and versions without any problems. Additionally, the same production .ipa file downloaded from Firebase is functioning as expected.

Hello everyone and thank you for you're time! I got an issue with uploading several icons to testflight. I'm using Game Maker Studio as my engine for the game. This is the error that I'm getting, even when I try to use the old icons for the game, that worked in the past. I tried to transform the icons, using this site "https://makeappicon.com/", but I still got the same validation error. Can you help me fixing the issue - thank you so much!

Hello, I uploaded my application to TestFlight via Xcode (React Native), but I cannot install it on my device or other testers' devices(Internal). This happened to all builds, all my apps and all tester's I have faced this error before, but after sending a support ticket, it was resolved. But this time, it's come back. I don't know why.

Hi, We are working to integrate the Live Caller ID Lookup feature into our app. After submitting the request form via the link: https://developer.apple.com/contact/request/live-caller-id-lookup/, we received this reply from Apple: Apple’s OHTTP relay has been configured to talk to your OHTTP gateway. Now Live Caller ID Lookup should work for your application extension when distributed through App Store. However, before officially releasing our app on the App Store, we’d like to make sure the Live Caller ID Lookup feature is working as expected. To test this, we uploaded the app to TestFlight, and it successfully passed App Review. However, the test failed — we observed that the system tries to fetch the config from http://www.example.com/config instead of our actual configuration URL. Questions: Is this expected behavior when using TestFlight? Does the Live Caller ID Lookup feature only become active after full public release on the App Store? Is there any recommended way to test this feature before public release? Thank you!

I built a TestFlight version of my unpublished app. While using it, I wanted to test out the subscription purchase and when I did, I used my real production Apple ID and not a Sandbox test account to purchase the subscription. I was surprised to see that it worked and I was able to use the test subscription in the app. However, I now have no way of canceling it. It has renewed every day at the same time due to the accelerated TestFlight subscription rate (it's a monthly sub). I read that it should stop auto-renewing after the 6th time, but I believe it's been over a week now and it still hasn't cancelled. I understand that it's not a real purchase, but I would still like to cancel it so I can try it without the purchase again using this account and also use it with a different Sandbox account. Can someone help me with canceling it? Since the account I used was not a Sandbox account, I can't just clear the purchase history in App Store Connect. Also, I can't go into my personal account settings to remove the subscription since it's not a production one.

Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Store Connect overview. In contrast, in another app (using the same workflow and also Icon Composer), everything works perfectly: the icon shows up on the device, in TestFlight, and in App Store Connect. Has anyone experienced a similar situation? Is there something specific that needs to be set in App Store Connect (e.g. Marketing Icon / Branding section), or could this be related to the new iOS 26 icon handling? Any help or hints would be greatly appreciated. Thanks in advance!

After upgrading to macOS 26, I cannot install or update my app from either the App Store or TestFlight. Other apps update and install normally. Steps: Before upgrading, the app was installed via TestFlight and worked fine. After upgrading, I tried to update the app from the App Store: The update stalls at ~90% and never completes. Other apps update successfully. I launched the already-installed TestFlight version — it worked. After deleting the app, I tried reinstalling from TestFlight and got the error: “The app couldn’t be downloaded. Try again.” I tried rebooting, logging out/in of my Apple ID, and submitting a new TestFlight build — same issue. Environment: Originally built with Xcode 14 Also tried a new build with Xcode 16 App is compatible with macOS 26. Distribution outside the App Store (Developer ID signed and notarized build) runs fine

Hi, yesterday when I was trying to release the TestFlight build of my app the xcode said that it could not authenticate my apple ID. I then came to know that it actually wanted me to complete and aggrement which was "Paid Apps Agreement". This agreeemnet is to be made if one has to sell their app on AppStore or make in-app-purchases. I want to ask if it was mandatory for me to sign that agreement? As the solution which I could come across suggested that xcode blocks the distribution if there is a pending agreement.

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.

I had everything working with Revenue Cat. Then my app got rejected for not loading subscriptions, which was odd because a previous built was rejected for wording on that same paywall. I checked, and realised I suddenly can't fetch products in testFlight either. I can only see products in Xcode using the store kit configuration file. I've found many issues like this online and everybody point to the same solutions (that seem to work for most), but here's what I tried so far: Checked that all my agreements in App Store Connect are active Checked that ids match between Xcode / revenue cat / App Store connect Store kit config file is syncing with App Store Connect correctly I removed revenue cat and used the store kit api directly to fetch products. The array of products is empty in all environments that don't have access to store kit config file. Checked status of all subscriptions (all waiting for review -- as they were when the paywall worked) Nothing seems to work... Any suggestions? Many thanks

Hello, I want to add an external test, but I encountered an error when creating the test information. The error message shows that the phone field needs to be filled with only numbers. The following is the error screen This page has one or more errors. Please make sure the contact phone number contains only numbers and try again. Cannot save name because there are other invalid fields. Cannot save last name because there are other invalid fields. Could not save email because there are other invalid fields. Has anyone else encountered the same situation? Thanks.