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.

Greetings to all! I recently developed an called DANZUB, the hub for dancers using the Adalo no-code tool. The App from adalo was directly imported into TestFlight on App Store Connect. When I released it for review, I got a rejection that app was not supported (display scale issue) on Ipad. I have primarily designed for IPhones and I do not know how I can adjust to IPads as well. I don't have this option on Adalo. Some said I could change the settings in XCode. But I don;t have the file, because the file was directly exported from Adalo to App Store Connect. I am unable to download the file. Please help, I am new to developing. So close yet so far. Thanks all!!

Recently started hitting the following error when trying to install the latest version of app I admin for in TestFlight: "The app couldn't be installed because your Apple ID or password is incorrect. Try Again" I've attempted to sign out / in of my Apple ID to no avail.

I uploaded several build on my testflight and all of them seemed to work. so I made update to my app version 1.0.7 and deployed it to testflight and it crashed. So decided to make a new update for the app resolving the crash issues and when I tried to install the app update was told "could install [app name] the profile can't be installed. Try again

I can't install or update any application on testflight. Profile not changed. In one time on all application I have same issue. And all members with team

We are getting the following error: "the profile can’t be installed. please try again later". any idea what could be the cause for such an error (Occurs on many users even after reinstalling TestFlight)

After I integrated the Facebook SDK into my app, I encountered an issue where I couldn't install the app after building it. When trying to install the app through TestFlight, I receive the following error message: "No se pudo instalar Plus Argentina. No se pudo instalar el perfil. Reintenta." I've attached a screenshot for reference: Has anyone experienced a similar issue or does anyone have suggestions on how to resolve this?

I'm trying to test an app on Testflight and having problems. I've uploaded my app to App store connect successfully and I've added my external testers to the new build. It's in the "waiting for review" stage. When I go to TestFlight, I see the new build, as expected (I'm an internal tester). When I tap "install" I get the following error: Could not install ______. The profile can't be installed. Try again. Is this a problem on my end or apple's? The same build of the app works fine when I hit the "run" button in XCode.

Hi Everyone, As a team from the company, Pearson (Located in Sri Lanka, the United States, the United Kingdom, India, Australia, China etc.) is working in the software quality engineering field and focusing on compatibility testing on browser versions and the OS versions available in the market. Right now we are facing an issue, especially in iOS devices where the number of users testing the Chrome beta in the TestFlight hit the threshold value (You can ONLY invite up to 10,000 external testers using their email address or sharing a public link.). As a result, we are unable to install the Chrome Beta on iOS devices to continue our compatibility testing which is critical for our application compatibility testing Anyone who does not test or use the Chrome beta app in the TestFlight anymore can delete the Chrome Beta app from the TestFlight.(It will decrease the number of registered users to less than 10,000 ) So that users like us who test our products with the Chrome Beta version will be able to register as Chrome Beta testers and can continue our testing without any hassle. It would be highly appreciated to let others who need to register as Chrome Beta testers in Test Flight to perform their testing

I have been trying to access the test flight since yesterday but was not able to access instead it displayed the below message. "Before you can start testing, a developer has to invite you to test one of their TestFlight apps.To accept an invite, click on the link in the email or enter invitation redeem code" - Attached the scrrenshot Once I clicked on redeem there is a pop-up displayed that asked me to enter the Test flight invitation code which I did not get. - Attached the screenshot This is purely to test the Chrome beta version to test the compatibility and not any personal apps. Can someone help me out to solve this issue?

Hi guys, I'm trying to make a test flight build (first time in a while) in Xcode 16.0 Beta for a visionOS 2.0 beta test. When I click Distribute App, It preps and creates the app but fails on the next step "creating app record..." with this code The operation couldn’t be completed. (DVTAppStoreConnect.ServiceBackendError error 1.) My account is old with a ton of certs, identifers, profiles etc. I've tied setting up a new one but that doesn't seem to fix the issue ( though I might have easily missed a step? ) Any help on how to solve this?

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.