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.

Lately TestFlight has been having unexpected delays for me. For context, I have an app that I am just testing internally right now, so whenever I have a new build the process I follow is: Upload build to App Store Connect Wait for build to finish processing (typically less than a minute) Add compliance info in App Store Connect Wait for build to be distributed via TestFlight For the last few months, after I entered the compliance info, my app would be available for TestFlight distribution almost immediately after I entered the compliance info. I would get the email notification and I could see my new build on TestFlight. I am getting the notifications from App Store Connect that my build has completed processing within a minute or two of uploading it. Then, I enter the compliance information in App Store Connect. Lately, it has been taking multiple hours in between when I provide the compliance info and when the new build is available on TestFlight though. So there is a seemingly random time period in between when I enter the compliance information and when the app is actually distributed to TestFlight. I am not sure why this process that used to be immediate now has multiple hours of lag. There also does not appear to be any way for me to manually check on the status or anything. After I enter the compliance info, it is an entirely hidden and automated process to then push that build out to TestFlight. Is there anything I can do to improve this, or are there any known causes for this issue? I have tried re-submitting another new build version to try and "flush the pipeline", and that worked once before, but it doesn't appear to be working anymore.

I use Expo EAS tool to submit to iOS and honestly I never had any issues before, at least on other projects. In the past few days I have been trying to submit a new build for an update of an older app but I am getting this error: A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. (ID: O4YFH7VPB2LECAUAVXR6G4WRFQ) (403) I checked my agreements page and there is no clear indication of any missing agreements left to sign or what not. I have tried different builds of this project to no avail. I am stuck in a rut and I have been already waiting three days for customer support to acknowledge my issue and get back to me.

I created a build and in the info.plist "Bundle version string (short)" is set to "$(MARKETING_VERSION)". In the project settings the marketing version is set 5.0 and this shows in Testfight. When I submitted the app for review I set the app store version number to 3.3. I know the app will appear in the appstore as v3.3. Before I release this app I need to know: What number will be returned by "infoDictionary?["CFBundleShortVersionString"]"? 5.0 or 3.3?

Hello, I am developing an iOS app using Expo React Native with TypeScript and the react-native-iap library for handling in-app purchases. However, I am facing issues when testing subscriptions. Issue Details Development Mode (Simulator & Physical Device): When the app initializes with withIAPContext, I immediately receive the error: E_IAP_NOT_AVAILABLE This prevents the app from fetching available subscriptions. TestFlight (Production Environment): The app does not render anything inside my SubscriptionsIOS.tsx component. No error messages appear, but the subscriptions do not load, and the UI does not display anything. Steps to Reproduce Open the app on an iOS simulator or physical device. Navigate to the SubscriptionsIOS.tsx component, where in-app purchases should be displayed. In development mode, the error E_IAP_NOT_AVAILABLE appears immediately. In TestFlight, the app does not crash, but nothing renders in the subscription screen. What I Have Done So Far ✅ Enabled In-App Purchases in Apple Developer and App Store Connect. ✅ Ensured my bundle identifier matches the one in App Store Connect. ✅ Set up a Sandbox account for testing purchases. ✅ Verified my react-native-iap implementation and restored transactions properly. I would appreciate any guidance on why E_IAP_NOT_AVAILABLE appears in development and why in-app purchases fail silently in TestFlight. Does Apple require additional steps for Expo-based apps to handle in-app purchases correctly? Thanks in advance for your help!

I have an issue when i use external tester with a public link and emails. Test fly is well installed but when i have to open the app, it just charge as seen in the screen.

I'm using App Store Connect API to automate onboarding/off-boarding user invitations for my team members when they start working on my app. Once devs join the team, I'd like to invite them to the specific app's beta test group. This requires some additional work after the user has joined the team because unlike visibleApps, there's no way to initially indicate the beta test groups that a user should have access to. One challenge I'm finding is that people don't immediately join the team on time so polling feels a bit excessive/wasteful. Is there some recommended mechanism for adding users to the internal test flight group, or is there a way to trigger a webhook when the list of users is updated. I noticed that there's a new /v1/marketplaceWebhooks API so I imagine this is the recommended format for registering callbacks. Any assistance here would be greatly appreciated.

The endpoint /v1/betaAppReviewSubmissions supports post and get requests for creating and querying beta app store review submissions but I would like to be able to withdraw submissions by making a delete request like you can on the website and when using cookies authentication to the same endpoint with tools such as with Fastlane. Is this API intentionally missing in the official API or is it something that could be added?

I'm testing my app on a Testflight before release. Right now I haven't pass my review yet (was rejected). When I go to Settings > My name > Subscriptions I can see my subscription with an empty thumbnail(no app logo). Could anyone know how to solve this issue?

Hi - I've added in-app purchases (Quarterly and Yearly ) to my app and submitted it for TestFlight. The app is available, but in my Developer account, the in-app purchases section still shows the products as 'Waiting for Review.' When I test the app for in-app purchase, the dialog does not appear. Is this issue of "Approval" of the in-app purchase product? If YES, how can I get approval for these in-app purchase products? FYI: I have attached a screenshot of the in-app purchase products. Please suggest Thanks, Sushil

Hello everyone. As new versions come out, I find myself with a collection of versions I'd like to purge. I started requesting build expiration, but it takes a long time and outdated versions remain visible. How do I remove all these entries?

In App Store Connect I've uploaded a new build, but I'm unable to distribute the App to my tester groups - including internal. The internal group is grayed out. I am able to Select an External group but they actually do not receive any email notification nor do they see any update within their TestFlight App. I've attempted to upload the build a few times, including old builds which had been distributed in the past to no avail. I'm not able to distribute to any tester group, please advise.

We have a rather complex network of dependencies for our application stack and, from it, we create multiple unique executables that are placed into the Contents/MacOS directory of our bundle. MyApp.app `- Contents/ `- Frameworks/... `- MacOS/ `- exec_a `- exec_b `- Resources/... Both executables require the same dependencies (and use the same shared .dylib files built as targets in the same project) so it makes sense for them to be in the same place rather than in their own .app folder as I understand it. Qt Libs -> core_lib.dylib -> gui_lib.dylib -> exec_a `-> exec_b etc. We've confirmed build artifacts are correct and the rpath/dependencies are all clean. When in development, all executables run as expected and we can command exec_a (the executable we're listing in the primary Info.plist) to launch exec_b at any time. Once the bundle is signed, however, we cannot get exec_b to launch in any capacity. Even lldb dies right away because it can't attach to anything. We assume this is something in the gatekeeper area of blocking these additional executables. We get the following when trying to run those additional exes in any way: Trace/BPT trap: 5 We're using macdeployqt to finalize the bundle and bring in the correct packages - perhaps something it's doing is causing the additional executables to fail or we're missing an entitlement. We've submitted the app to TestFlights successfully even with these invalid executables to see if there was something the processing of the app would find but so far nothing. We've seen other example of applications with multiple executables in the same MacOS directory and are wondering what the difference is. Any hints or guidance would be great. Thank you!

I archived and distributed a new version of my app (with new build number) and it shows up in the Appstore connect (no issues here). But the new version doesn't show up in the Testflight app, nor did the internal testers receive any email regarding the new update. I have waited for 3 hours now, and still no progress on this. This issue is happening out of the blue. The whole process was working fine yesterday. I did a couple of things to debug this issue, along with: Changed build version couple of times Reset provisioning profile Created new testing group, added users, added build manually No matter what I do, I'm unable to get the new version of the app to show in the Testflight app for my internal testers. I have also contacted apple support via email, waiting for their response. Any help appreciated! Thanks

Hello, I uploaded a new iOS build (1.0.1 - Build 180) to App Store Connect for my app "Benimle Konus". The build has been processed successfully and is marked as "Ready to Test". However, when I try to assign this build to any internal TestFlight group, the group checkboxes are greyed out and cannot be selected. I’ve made sure that: All required metadata is filled out. What’s New and compliance information is complete. Previous builds worked with the same TestFlight groups. To fix this, I have uploaded 3 separate builds, but the issue still persists with all of them. There are no error messages, but I can't continue testing because I can't assign the build to testers. App ID: 6742759002 Bundle ID: com.benimlekonus.app Build Version: 1.0.1 (180) Is this a known issue or something I'm missing? Any help would be appreciated.

I cannot test IAP using sandbox account that I logged on from settings, it keeps show my regular Apple ID when I try to test IAP from TestFlight This issue frustrate me and bunch of my colleagues, we cannot manage our subscription when sandbox account is default choosing Apple ID I've seen people complaining about this issue a lot Any help on resolving this issue would be really appreaciated

I have two platform for my IOS app, tvOS and IOS , i created group by Manual Distribution in TestFlight, and added testers and build, But i see No Builds Available status in my tester account, and invitation also does not send

I am working on an iOS app using Flutter that tracks outgoing calls using CallKit. The call tracking functionality works perfectly in Debug mode but does not work when the app is published to TestFlight. I have already added Background Modes (voip, audio, processing, fetch) in Info.plist. I have added CallKit.framework in Xcode under Link Binary With Libraries (set to Optional). <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>aps-environment</key> <string>production</string> </dict> </plist> These are the necessary permission which I used in info.plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>BGTaskSchedulerPermittedIdentifiers</key> <array> <string>com.agent.mygenie</string> </array> <key>CADisableMinimumFrameDurationOnPhone</key> <true/> <key>CFBundleDevelopmentRegion</key> <string>$(DEVELOPMENT_LANGUAGE)</string> <key>CFBundleDisplayName</key> <string>MyGenie</string> <key>CFBundleDocumentTypes</key> <array/> <key>CFBundleExecutable</key> <string>$(EXECUTABLE_NAME)</string> <key>CFBundleIdentifier</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER)</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>mygenie</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>$(FLUTTER_BUILD_NAME)</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>$(FLUTTER_BUILD_NUMBER)</string> <key>LSRequiresIPhoneOS</key> <true/> <key>NSCallKitUsageDescription</key> <string>This app needs access to CallKit for call handling</string> <key>NSContactsUsageDescription</key> <string>This app needs access to your contacts for calls</string> <key>NSMicrophoneUsageDescription</key> <string>This app needs access to microphone for calls</string> <key>NSPhotoLibraryUsageDescription</key> <string>This app needs access to photo library for profile picture updation</string> <key>UIApplicationSupportsIndirectInputEvents</key> <true/> <key>UIBackgroundModes</key> <array> <string>voip</string> <string>processing</string> <string>fetch</string> <string>audio</string> </array> <key>UILaunchStoryboardName</key> <string>LaunchScreen</string> <key>UIMainStoryboardFile</key> <string>Main</string> <key>UISupportedInterfaceOrientations</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array> <key>UISupportedInterfaceOrientations~ipad</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array> [code.txt](https://developer.apple.com/forums/content/attachment/0a327dbd-652e-41d5-8811-c462d09e0567) </dict> </plist> And below is the file are AppDelegate.swift, call_tracking_mixin.dart, & main_call.dart file for full knowledge

Hello, I uploaded a new build to TestFlight, and it has been about an hour since the processing was completed. However, the update is still not showing up in the TestFlight app. From my experience, the update usually appears within 10 to 30 minutes, but this time it is taking unusually long. I’m wondering if anyone else has experienced a similar issue and found a solution. Any advice or guidance would be greatly appreciated. Thank you!

Seems that recent TestFlight update (3.8.0) is broken on iOS 14.1. It crashes on launch. It worked fine on the same device just few days ago (I assumed it was 3.7.1). I uninstalled the TF and installed it again but it doesn't help. Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 0 Attached is the crash report. I would appreciate if you guys can quickly fix it, or provide a solution. Thank you. Crash report

My application is in flightTest mode. I received my first two crash reports in XCODE /Organizer. The context is well described, and I was able to isolate the locations where very serious errors occurred. My application is connected. I'm missing one piece of data in this crash report: the time of the crash. This will help me see what (in my case) static data was being read on the data server at that time. This will help me investigate. Is it possible to obtain this information?