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.

Before I launched my app, I ran a TestFlight beta program and also included a one time purchase in the TestFlight build to test the functionality. Now that the app is available in the App Store, I had closed the TestFlight program, but am looking to reopen it again to test iOS 18 specific features. The issue is, the beta testers that previously purchased the IAP on TestFlight but didn't actually purchase the IAP on the App Store version would be able to use the paid features of the app for free as long as they have the TestFlight build. Therefore I would like to revoke all the purchases made via the TestFlight build. Is there any way to do that?

I hope I'm wrong on this one, but as far as I understand watchOS is not able to collect/ capture Mach Exceptions and Signals. Which is the majority of crashes happening on watchOS. I'm looking for a proper way to automatically receive crash reports from a watchOS app. If this truly is a system limitation there's no way any tool can workaround it. Does anyone know of a workaround or tool to automatically collect crashes on watchOS? (I'm aware that it's possible to do so manually)

I have read and tried all the possible solutions available online, but still didn't get a result. My multi-platform iOS/macOS app uses private databases in iCloud with Core Data. All works as expected when I build the app from Xcode to my multiple devices: data is being synced. But when I upload the app to TestFlight, data is not being synced. This is what I have already tried: In CloudKit Dashboard, I reset the schema and deployed schema changes from the development to production. In Xcode project settings, in Targets, under Frameworks, Libraries... I added the CloudKit.framework, set as "do not embed". In Xcode project settings, under Signing & Capabilities, all the CloudKit, Background fetch and Remote notifications checkboxes are enabled for both Debug and Release. They all point to the same correct iCloud container. In Xcode project settings, under Build Settings, Code Signing Entitlements for both Debug and Release point to the same entitlements file. In .entitlements file, CloudKit container identifier points to the correct container. iCloud Services set to CloudKit. In .entitlements file, APS Environment for both iOS and macOS is set as "production". In Core Data .xcdatamodeld file, under Configurations, I have a Default option, and it is being set to "Used with CloudKit." Each time I upload new version to the TestFlight, I delete all the previous versions from all my devices, so development and production containers are not mixed up in any way. I understand that I may be missing something. But after researching all the resources available online, I didn't find anything else to configure or to add in this setup. I want to point out again that data is not being synced only in TestFlight, and thus, possibly, after release. Whenever I build app directly to the device from Xcode, all works as expected. I hope someone can help me.

Hi, I'm unable to add the 3rd build of my TestFlight app to any external testing group (but I can for an internal testing group). The 2nd build was successfully added to an external testing group, the 3rd build has the status "Ready to test", and I've expired all other builds. I've also completed the "What to test" section in English (U.K) and English (U.S). Any idea what I might be doing wrong? Thanks!

Hello, I have a working App which archives and distributes ok. However I receive a message in Xcode (15.2) after a few minutes saying app "is not a valid binary". The app is not added to available Builds in TestFlight on App Store Connect. Is there a way of finding out what is going on ? or a likely reason for this error ? Thanks

https://api.appstoreconnect.apple.com/v1/betaTesters/{id} Cannot call delete on any of the above Cannot be uninstalled from the app store console (IDs cannot be provided as personal information) { "errors": [ { "status": "500", "code": "UNEXPECTED_ERROR", "title": "An unexpected error occurred.", "detail": "An unexpected error occurred on the server side. If this issue continues, contact us at https://developer.apple.com/contact/." } ] }

Hi team, I cannot delete Testers from TestFlight. The following error message keeps popup. "An error has occurred. Try again later." Do you have any ideas? Thanks in advance!

I want to have my app tested by friends before uploading to App Store. How is it possible??

2024_06_09_testflight_launch_crash_log.txt Running my macOS app the first time after installing via TestFlight crashes on launch. Every subsequent run works fine (including completely quitting the app and re-running it). Also, building and running directly in XCode both in Debug and Release mode works fine. I'm on a Mac M2 and the app excludes x86_64 arch. Here is the trimmed crash log (sanitised full log is attached) Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: CamHero-macOS-v2-Release [12876] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18c81d11c __pthread_kill + 8 1 libsystem_pthread.dylib 0x18c854cc0 pthread_kill + 288 2 libsystem_c.dylib 0x18c764a40 abort + 180 3 libglib-2.0.0.dylib 0x1061e5bd0 g_assertion_message + 464 4 libglib-2.0.0.dylib 0x1061e5c44 g_assertion_message_expr + 116 5 libgstlibav.dylib 0x10549ede0 gst_ffmpeg_cfg_init + 776 6 libgstlibav.dylib 0x10548a4f4 plugin_init + 140 7 libgstreamer-1.0.0.dylib 0x10646a458 gst_plugin_register_func + 636 8 libgstreamer-1.0.0.dylib 0x106469fe4 gst_plugin_register_static + 212 9 libgstlibav.dylib 0x10548a45c gst_plugin_libav_register + 92 10 CamHero-macOS-v2-Release 0x104a01624 gst_ios_init + 900 (gst_ios_init.m:1072) 11 CamHero-macOS-v2-Release 0x104a80590 specialized CamHeroMacOSApp.init() + 68 (CamHeroMacOSApp.swift:19) 12 CamHero-macOS-v2-Release 0x104a804a4 CamHeroMacOSApp.init() + 4 [inlined] 13 CamHero-macOS-v2-Release 0x104a804a4 protocol witness for App.init() in conformance CamHeroMacOSApp + 20 (<compiler-generated>:16) 14 SwiftUI 0x1b7f134e0 0x1b7163000 + 14353632 15 CamHero-macOS-v2-Release 0x104a804d8 static CamHeroMacOSApp.$main() + 24 [inlined] 16 CamHero-macOS-v2-Release 0x104a804d8 main + 36 17 dyld 0x18c4d90e0 start + 2360 Thread 1: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 2: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000600000755680 x5: 0x0000000000000020 x6: 0x0000600000755680 x7: 0xffffffff00008600 x8: 0x8ddd1ea266cd729b x9: 0x8ddd1ea3846d2c5b x10: 0x0000000000001620 x11: 0x00000000dbe367fb x12: 0x00000000000007fb x13: 0x00000000000007fd x14: 0x00000000dc03683c x15: 0x000000000000003c x16: 0x0000000000000148 x17: 0x00000001eb9f3da0 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x00000001e2a05ec0 x21: 0x0000000000000103 x22: 0x00000001e2a05fa0 x23: 0x000000016b407508 x24: 0x0000000000000000 x25: 0x00000001064f8450 x26: 0x000060000080d511 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016b407460 lr: 0x000000018c854cc0 sp: 0x000000016b407440 pc: 0x000000018c81d11c cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 Address size fault It seems that the initialisation of one of the gstreamer plug-ins doesn't go well. But, I wonder what might lead to that happening only the first time after launch? Will appreciate any clues! EDIT / UPDATE: If i remove the app completely and install the same version again from TestFlight, app doesn't crash. So it seems the crashing is limited to the very first launch of a new /updated version.

Hi! We are a large team developing an app in several squads and using Testflight for distributing builds to our QA team. We have a pipeline in place that automatically publishes new builds using AZ Pipelines. After 20 or so uploads in a day we are getting the following error: 2024-05-27T18:23:52.9078410Z 2024-05-27T18:23:52.9081600Z [18:23:52]: [altool] { 2024-05-27T18:23:52.9082060Z 2024-05-27T18:23:52.9082930Z [18:23:52]: [altool] NSLocalizedDescription = "Asset validation failed"; 2024-05-27T18:23:52.9083110Z 2024-05-27T18:23:52.9084350Z [18:23:52]: [altool] NSLocalizedFailureReason = "Upload limit reached. The upload limit for your application has been reached. Please wait 1 day and try again. (ID: 7bfc7cad-3026-4b6a-a18b-32b1bf3de218)"; 2024-05-27T18:23:52.9086960Z 2024-05-27T18:23:52.9088610Z [18:23:52]: [altool] "original_server_error" = { 2024-05-27T18:23:52.9093640Z 2024-05-27T18:23:52.9094740Z [18:23:52]: [altool] code = "STATE_ERROR.VALIDATION_ERROR.90382"; 2024-05-27T18:23:52.9095230Z 2024-05-27T18:23:52.9096600Z [18:23:52]: [altool] detail = "Upload limit reached. The upload limit for your application has been reached. Please wait 1 day and try again."; 2024-05-27T18:23:52.9097920Z 2024-05-27T18:23:52.9098990Z [18:23:52]: [altool] id = "7bfc7cad-3026-4b6a-a18b-32b1bf3de218"; 2024-05-27T18:23:52.9099180Z 2024-05-27T18:23:52.9099360Z [18:23:52]: [altool] status = 409; 2024-05-27T18:23:52.9099490Z 2024-05-27T18:23:52.9099690Z [18:23:52]: [altool] title = "Asset validation failed"; 2024-05-27T18:23:52.9099810Z 2024-05-27T18:23:52.9100010Z [18:23:52]: [altool] }; 2024-05-27T18:23:52.9100090Z 2024-05-27T18:23:52.9100570Z [18:23:52]: [altool] } I cant seem to find any documentation stating upload limits for an app within a day or timeframe. Can you tell me if there is a limit that my account or app has for daily builds. It could help us streamline our development build distribution.

Hi i am getting since days the error in App Store Connect when I want to release a build for a test flight group: "An error has occurred while processing your enquiry. Please try again later." It was working for 2 years but since a few days not. Do you have any ideas?

Hi everyone, hope someone can help me. I have received an invitation to join a development team, when i press on "Accept invitation" i am redirected to this page: https://appstoreconnect.apple.com/login?subType=COMPANY&activationKey=xxxx&providerName=***&username=xxxx The page ask for my Apple ID credential, but when i prompt it it show a spinning loader and the it ask for my credential again infinitely, without any error or message. In the general header, there is the Status Code = 400 Bad Request I am getting the following response from the update API : "data" : { "errorString" : "ITC.multipleProviderInterstitial.invitationInvalid.title", "providerId" : null, "publicProviderId" : null }, "messages" : { "warn" : null, "info" : null, "error" : null }, "statusCode" : "SUCCESS", "links" : null } Can someone help me out in this?

I'm working on this Mac Safari extension https://apps.apple.com/app/id6464076425 The installation of the app via Testflight stops without any success (only for me) As well as the installation via AppStore. This happens only to me. I tried it on another computer, and it installed successfully. Here are some videos: This makes the development and release process impossible until I solve this problem. I tried all the methods I could find online, such as: Deleting the currently installed app Restarting Safari Restarting my Mac Is there anything else I can do to fix this problem?

I have an app in the App Store that doesn't need to be sandboxed (it's been in the MAS since 2010, before sandboxing became mandatory for new apps). I have run into an obscure bug that ONLY appears when the app was installed by TestFlight, but not when I run the same executable from before the upload (taken from the very same archive). I suspect it's a bug around the installed receipt or is codesign related, because that's the only things I am aware of that would be changed between my upload and the re-download via TestFlight. To debug this, I have built a small test project that I want to submit to DTS, demonstrating the bug in a clear and direct manner. But when I try to upload it, even for "internal testing" only, the upload gets rejected automatically because it's missing the App Sandbox entitlement. However, if I add the entitlement, then my app won't work, so I cannot enable it. Hence I need to get an exception from App Review so that they allow me test app being uploaded without the sandbox entitlement. I know that's possible because otherwise I'd not be able to upload my regular application, which I did just the other day. How do I get this resolved? Would a member of the App Store team please contact me? The Apple ID for the test project is: 410006334. Or, alternatively, you can also use the newer 6503298614 (I tried the other in hopes it would be allowed not to be sandboxed because I had created it long ago, but that didn't work out).

Has anyone else seen this happen with their macOS apps in TestFlight? The situation: When I launch my app that's been downloading via TestFlight.app, it often comes up with its main window deactivated. Also, when I have open more than one window and close one, the other window doesn't come to front either. In either case, activating the app or clicking into a window will activate it properly. It feels as if there's another window that's not visible but somehow keeps getting activated. I have this happen on two Macs running both Sonoma and Monterey. Also, if I take the very same build that I had uploaded to TestFlight and run it directly, it works correctly. So I suspect that TestFlight somehow messes with my app's windows. If you want to test this yourself: Get the app thru this link: https://findanyfile.app/TestFlight/ Then launch it. Often, the Find window will already come up without being active. Activate it, then open the Preferences window by typing cmd-comma. Then close the Prefs window with cmd-W. This should re-activate the Find window but will instead leave it deactivated, and none of the menu shortcuts (such as cmd-comma, cmd-N or cmd-Q) work. That's the bug. I wonder how I can debug this to find a work-around for this odd behavior. E.g, I'd like to see if there is indeed a semi-hidden window causing this. How would I do this? I could probably make a new TestFlight build that queries the app's windows array and logs it. But are there other ways to query an app's windows? I tried AppleScript, but since my app isn't scriptable, I only get an error -1728 for tell app "Find Any File" to get windows.

Imagine you accidentally made a build of your app with version 2 and uploaded that to App Store Connect for TestFlight even though you're still working on version 1.x and continue to do so with your public releases. Here's an example: The build 55 is the accidental 2.0 version, but the current releases are 209 and 210 with a lower string version. So, that one build of version 2 was a mistake. Sadly, you cannot remove it, even it has expired, even if it has never seen the outside of TestFlight. And it's a bit annoying too, because it stays up there at the top of your builds, and always presents the outdated version when you visit that page on App Store Connect. But worse is the fact that because of this, any version 1.x you release since then will not get you any crash reports or feedback that the user may have submitted to you. This is clearly a bug, and I was able to verify this just recently. I suspect this happens because Apple wants to avoid storing and forwarding reports for outdated versions, maybe to save space on their servers. That makes somewhat sense, though I've also had people finding crashes in older versions that were not fixed in the latest version, so I'd still like to get those reports from older versions. However, if Apple really only wants to keep crash reports and feedback msgs from the latest release, then Apple's mistake is that they use the unreliable string version to check which is the latest version instead of using the build number, which is ENFORCED by Apple to always be incrementing for each upload. If you are in the same boat, please comment so that we can make it clear to Apple that this is not an isolated issue.

Update: Turns out it works for others, apparently, and I also found one of my Macs where it does work, too. So it must be something pertinent to my systems. Oddly, though, the same ones where it now fails used to work because I had TestFlight enabled there before. I have TestFlight set up on App Store Connect, and I have already about 50 testers subscribed. Today, I found that the Public Link does not work any more: Once TestFlight.app is installed, and one clicks the link to add my app to TestFlight, it always shows the error ""Unable to Open Link" in TestFlight.app: I've tried this on several Macs (Ventura and Sonoma), and with different Accounts, both where the app was already added or not. Is something generally broken, i.e. do others see the same issue with their TestFlight links, or is it just me? How do you suggest I get this resolved? Here's an example link I set up for this purpose - it only allows a handful of subscribers, so please do not actually subscribe but just see if you even get allowed to, or if you get the same error if you must try: https://testflight.apple.com/join/oV8NNojg And here's how it's set up:

Hi, I would like to know if ios 17 sdk is compatible with react native version 0.64. I am not able to build my app currently.. Error that i got when build Undefined symbols for architecture x86_64: "_GULLogBasic", referenced from: _MLKLog in MLKitCommon[x86_64]7 "OBJC_CLASS$_AppCenterReactNative", referenced from: in AppDelegate.o "OBJC_CLASS$_AppCenterReactNativeAnalytics", referenced from: in AppDelegate.o "OBJC_CLASS$_AppCenterReactNativeCrashes", referenced from: in AppDelegate.o "OBJC_CLASS$_FKUserDefaultsPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperClient", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitLayoutPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitNetworkPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitReactPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_GDTCORTransport", referenced from: in MLKitCommon[x86_64]6 "OBJC_CLASS$_GTMLogMininumLevelFilter", referenced from: in MLKitCommon[x86_64]200 "OBJC_CLASS$_GTMLogger", referenced from: in MLKitCommon[x86_64]26 OBJC_CLASS$_MLKITx_GIPLoggingReroutingGTMLogger in MLKitCommon[x86_64]200 "OBJC_CLASS$_GTMSessionCookieStorage", referenced from: in MLKitCommon[x86_64]26 "OBJC_CLASS$_GTMSessionFetcher", referenced from: in MLKitCommon[x86_64]26 "OBJC_CLASS$_GTMSessionFetcherService", referenced from: in MLKitCommon[x86_64]18 "OBJC_CLASS$_GULCCComponent", referenced from: in MLKitCommon[x86_64]11 "OBJC_CLASS$_GULCCComponentContainer", referenced from: in MLKitCommon[x86_64]3 "OBJC_CLASS$_GULCCComponentType", referenced from: in MLKitCommon[x86_64]3 "OBJC_CLASS$_GULUserDefaults", referenced from: in MLKitCommon[x86_64]2 "OBJC_CLASS$_RCTBundleURLProvider", referenced from: in AppDelegate.o "OBJC_CLASS$_RCTLinkingManager", referenced from: in AppDelegate.o "OBJC_CLASS$_ReactNativeNavigation", referenced from: in AppDelegate.o "OBJC_CLASS$_SKDescriptorMapper", referenced from: in AppDelegate.o "OBJC_CLASS$_SKIOSNetworkAdapter", referenced from: in AppDelegate.o "OBJC_METACLASS$_GTMLogger", referenced from: OBJC_METACLASS$_MLKITx_GIPLoggingReroutingGTMLogger in MLKitCommon[x86_64]200 "_kGTMSessionFetcherStatusDomain", referenced from: ___69-[MLKModelDownloader beginModelDownloadWithURL:modelInfo:conditions:]_block_invoke.285 in MLKitCommon[x86_64]18 ___150-[MLKITx_PHTHeterodyneSyncer batchSyncWithAccounts:syncedScopes:fetchReason:throttlingCache:heterodyneSyncInfo:accountToAuthToken:lastError:callback:]_block_invoke in MLKitCommon[x86_64]48 ___91-[MLKITx_PHTInternalHeterodyneSyncer syncHoldingLockWithSyncedScopes:fetchReason:callback:]_block_invoke in MLKitCommon[x86_64]51 ___63-[MLKITx_GMVCloudVisionClient initWithCloudUri:apiKey:options:]_block_invoke in MLKitVision[x86_64]7 ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Undefined symbol: _GULLogBasic Undefined symbol: OBJC_CLASS$_AppCenterReactNative Undefined symbol: OBJC_CLASS$_AppCenterReactNativeAnalytics Undefined symbol: OBJC_CLASS$_AppCenterReactNativeCrashes Undefined symbol: OBJC_CLASS$_FKUserDefaultsPlugin Undefined symbol: OBJC_CLASS$_FlipperClient Undefined symbol: OBJC_CLASS$_FlipperKitLayoutPlugin Undefined symbol: OBJC_CLASS$_FlipperKitNetworkPlugin Undefined symbol: OBJC_CLASS$_FlipperKitReactPlugin Undefined symbol: OBJC_CLASS$_GDTCORTransport Undefined symbol: OBJC_CLASS$_GTMLogMininumLevelFilter Undefined symbol: OBJC_CLASS$_GTMLogger Undefined symbol: OBJC_CLASS$_GTMSessionCookieStorage Undefined symbol: OBJC_CLASS$_GTMSessionFetcher Undefined symbol: OBJC_CLASS$_GTMSessionFetcherService Undefined symbol: OBJC_CLASS$_GULCCComponent Undefined symbol: OBJC_CLASS$_GULCCComponentContainer Undefined symbol: OBJC_CLASS$_GULCCComponentType Undefined symbol: OBJC_CLASS$_GULUserDefaults Undefined symbol: OBJC_CLASS$_RCTBundleURLProvider Undefined symbol: OBJC_CLASS$_RCTLinkingManager Undefined symbol: OBJC_CLASS$_ReactNativeNavigation Undefined symbol: OBJC_CLASS$_SKDescriptorMapper Undefined symbol: OBJC_CLASS$_SKIOSNetworkAdapter Undefined symbol: OBJC_METACLASS$_GTMLogger Undefined symbol: _kGTMSessionFetcherStatusDomain Linker command failed with exit code 1 (use -v to see invocation)

We created an app for iphone which includes a Watch app. The app works well during debugging, and also in TestFlight the Watch app installs nicely and does what it is supposed to do. However, when we make the app available through the Apple Business Manager (the app is for internal use by a company) the Iphone app downloads without problems, but the app for the Apple Watch does not work. When I go to the Watch app on my Iphone (where you can manage the apps on your Watch and so on) my app is listed, but when I press install I see a loader for a few seconds, then it stops but nothing else happens. So the code seems to be good, but after I download the app with a code through the Business Manager, then I cannot install the Watch version of the app.

I faced thta issue 2 days ago and today. The distribution certificat is installed in thekeychain and provision profiles gives no error when I'mm builing the arhive. But when I select App Store Connect as distribution. method it gives me an error that "App Store Connect access for ___ is required. What is the reason of that? Did someone face the same issue recently? Restart XCode and laptop did not help. I used to distribute the builds for individual account this way many times, but. now smth seems. to be changed or broken.