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.

The application was initially written in Swift, and we released an update where the app was rewritten in Flutter. Currently, we are adding a widget natively written in SwiftUI to the Home screen. The widget updates are managed by BGTaskScheduler. In BGTaskScheduler, an API request is made to fetch the latest data. The data is then processed to calculate an average value, which is subsequently sent to UserDefaults. The widget displays data fetched from UserDefaults. The minimum update interval is set to 30 minutes. When testing the widget updates through a build in Xcode, the widget updates as expected at the specified interval. However, when this build was provided to users via TestFlight, the widget does not update for them. Could this issue be related to TestFlight’s resource limitations? Is there any guarantee that releasing this version will ensure the widget updates correctly for users?

Hello, I have a some problem with background fetch. In my app I use background modes for fetch data and display on my home widget iPhone. Its working correct when I built app on my phone from Xcode but when I distribute my app on TestFlight my home widget not updating at all. Help me understand if this issue is only due to TestFlight resources, or should I try releasing the app and hope that it will work in the release version?

Not using beginRefundRequest like method from client side code, Can I ask apple to refund specific order from website or help center? If it possible where is the ask to refund menu in appstore connect or other?

Hi, I’m a developer working on iOS applications, and I need access to a TestFlight invitation code. This will help me test [briefly describe your purpose, e.g., a beta app or a tool]. Could you please provide me with the code or guide me on how to access it? Thank you so much! Best regards, [Edris Rahimi]

My iOS app has been in beta via TestFlight for 2 months without any issue. I use FlutterFlow and Firebase for my app build. I added the RevenueCat paywall and entitlement queries per their integration documentation. Within an hour or two of testing paid app subscriptions I lose access to iMessage on my iPhone and when I call Apple they say it's because the device/number has been reported as spam. This has now occurred on two separate devices with two different cell carriers which is frustrating since Apple representatives mention that they only perform a "one time exception" to reinstate iMessage privileges. The paywall and subscription to content is working perfectly. However, I don't feel confident releasing the app until I can confirm this won't happen to customers in production. I have no clue how to begin to test and troubleshoot this sort of issue outside of risking my personal phone numbers since it seems out of my control. Any insight or ideas?? Thanks so much!

I published an app to TestFlight today and the invitation email has the wrong company name. The invitation has the correct icon image and below it, the [app name] By [company name] for iOS. The problem is, the company name is actually a different app name that I had reserved and not the name of the company for which the developer account is associated. How do I ensure that future builds will have the correct company name in the TestFlight invitations?

I'm trying to add Cloud Kit integration to SwiftData app (that is already in the App Store, btw). When the app is installed on devices that are directly connected to Xcode, it works (a bit slow, but pretty well). But when the app is distributed to Testflight internal testers, the synchronization doesn't happen at all. So, is this situation normal and how can I test apps with iCloud integration properly?

I am developing a watchOS app that uses the uses the Fall Detection API. After requesting the entitlement, and receiving the entitlement and adding it to my app, I managed to implement the feature, and run the app on the simulator in Xcode and it works fine. But when I try to distribute the app to TestFlight internal testing, Xcode refuses and shows the following message: "Provisioning profile failed qualification: Profile doesn't support Fall Detection Notifications" and "Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.health.fall-detection entitlement" I am using an Xcode managed provisioning profile, and when I checked the profile from "signing and capabilities", it says that the fall detection capability and the entitlement are included in the profile. When I check my app's capabilities from "Certificates, Identifiers & Profiles" in the apple developer website, it says that the fall detection capability for my app has provisioning support for Ad hoc and Development only, is this the reason why I can't upload my app to TestFlight, or am I missing something? If it is the reason, then is there a way to change the provisioning support so that I can distribute the app? Thanks in advance

Can I use the TestFight app icon to link to my app inside TestFlight? All I found is this forum post that does not give a precise answer. Should I contact https://www.apple.com/legal/contact/trademark-information.html for that matter? Thank you

Apple 403 detected - Access forbidden. This request is forbidden for security reasons - The API key in use does not allow this request Error: submit command failed. this is the result from EAS expo when i am trying to submit the app build. according to my research its a bug of apple and must report it here in apple forum

Can someone give me a TestFlight code, I just wanna beta-test in peace without bullsh8 codes

I’m need invitation code to play Minecraft

Hello developers ! My team and I are currently trying to migrate to the new Xcode 16 version. We encounter a blocker problem with the new Xcode when submitting a new build on TestFlight. The problem : ITMS-90338: Non-public API usage - The app references non-public selectors in AccorHotelsApp: setSupportedInterfaceOrientations:. We tried several things to solve the issue : remove all the frameworks that are not built by us ; the issue is still present remove the code related to this API in our base code and the frameworks ; the issue is fixed remove only the code related to this API in our base code ; the issue is fixed This indicates that the problem is the code related to this API. The code removed : override public var supportedInterfaceOrientations: UIInterfaceOrientationMask { get { configuration.orientation } set { _ = newValue } } This code is located in our local SPM. It's used to handle orientation of our app depending on specifics configuration given as a parameter. Why Xcode 16 is detecting this API as a private one and consider this as an issue ? Is there a specific configuration we need to do in the local SPM package ? We are investigating on our side if we can find an alternative solution by changing this code, but this does not seem a bad usage as described in Apple documentation. Thank you for your help, Regards. RIVIERE Nicolas

How I can I have both versions of the app installed on the same phone? 1 for testing and 1 that’s live to see current version users are using? I had this setup before but now TestFlight installs replace the live version instead of the test version.

Hello, i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere. so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device. however when I try to archive and sent to Testflight/AppStore, I get: ITMS-90426: Invalid Swift Support and when I try to followup guides to create it manualy, copying libs from: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) plese here note, that ALL guides indicate to use folder "swift", however there are no *.dylib files... they are only in "swift-5.0" folder then I receive an error type: ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftSceneKit.dylib, libswiftCoreData.dylib, libswiftGameplayKit.dylib, libswiftUIKit.dylib, libswiftMetalKit.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftModelIO.dylib, libswiftWatchKit.dylib, libswiftDarwin.dylib, libswiftARKit.dylib, libswiftAssetsLibrary.dylib, libswiftSpriteKit.dylib, libswiftNaturalLanguage.dylib, libswiftCoreAudio.dylib, libswiftIntents.dylib, libswiftQuartzCore.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftVision.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftGLKit.dylib, libswiftSwiftOnoneSupport.dylib, libswiftXCTest.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/Filmtoro.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. here please also note that actually *.xcarchive does not contain any "Payload" folder, the package contains only two folders "dSYMs" and "Production/Applications/myapp.app" (inside it I can find "Frameworks" folder... this link was also very interested: https://indiestack.com/2017/03/implicit-swift-dependencies/ tho id didnt help a bit :) so what I would like to know, is what actually forces xcode to generate the SwiftSupport folder to the archive... the must be some direct setting inside *.xcodeproj/pbxproj which forces it... or dirrect setting in xcode/Build Settings which if not work I can submit an ticket to investigate. I am sure after a month of trying everything, whatever tip you can point out I already tried, however Please lets try everything again to get bottom of this. Many thanks for any tip

I'm having an issue with an app installation on my iPhone where it keeps installing the latest TestFlight version instead of the public App Store version. Here are the details: I initially installed version 1.24 of the app via TestFlight. I then uninstalled both the app and TestFlight and tried to reinstall the app from the App Store, which should be version 1.6 (the current public release). Despite this, the App Store keeps installing version 1.24, which is the TestFlight version. Here’s what I’ve tried so far: Uninstalled both the app and TestFlight. Restarted the iPhone to clear any cached data. Tried offloading and reinstalling the App Store app through Settings to clear its cache. Reinstalled only the App Store version, but the device still downloads the TestFlight release. Has anyone experienced this before? Are there additional steps I can take to reset the association to the App Store version? Any insights would be greatly appreciated. Thank you!

I’m encountering a problem with my iOS app with new Live Caller ID extension when uploading to TestFlight. Here’s what's happening: When I try to upload the app to TestFlight without the NSExtensionPrincipalClass, I get the following error: Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found in extension Info.plist for foo.app/PlugIns/bar.appex However, if I include the NSExtensionPrincipalClass in the Info.plist of my extension, the app fails to launch on both the dev build and through TestFlight. The error message I receive is: bar.appex with id <bundle_id> defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.live-lookup Has anyone experienced a similar issue? How to fix it?

I'm currently experiencing the same problem that many have had with error 422 "Beta contract is missing." I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem. I get the message "There was an error processing your request. Please try again later." And when I inspect with Safari it shows me this information: "errors" : [ { "id" : "9be0314c-3bd5-4143-a625-602322d7156e", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error "The requested app is not available or doesn't exist." Could someone tell me what process I should follow or where I can correctly generate the ticket for my error? Since the Apple support page does not load. Thanks!

Issue Submitting Builds for Beta Review - "Beta Contract is Missing" We are currently facing an issue in Testflight when trying to submit new builds for review for external Beta testing. Each time we attempt to submit a build in the "What to Test" dialog, we receive the following error message: "There was an error processing your request. Please try again later." Upon inspecting the browser response when clicking "Submit for Review" in the "What to Test" dialog, we found the following details: code: "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING" detail: "Beta Contract is missing." id: "4ed15cb2-2732-4100-a660-0899dcb0e25a" status: "422" title: "Beta contract is missing for the app." However, after checking the Developer Console, we are unable to locate any missing information or steps that need to be addressed. We would greatly appreciate your assistance in resolving this issue as soon as possible, as we are currently unable to push any new builds for testing. What we’re currently trying to do: Contact Apple Developer Support (no response for about 2 weeks) Create a new app bundle Build on a different machine/Mac Rebuild a previous version of the game that worked before Create a new app on another account (it worked, but the build was rejected—THANK YOU FOR NOTHING—because it’s considered a copy of our own game) We need to test before release, and we’re now three weeks behind our plans!

Problem: One of my QA Device crash while launch the iOS 15.5. Background: Previously, I update my os to macOS Sequoia & update my Xcode to 16 Release Candidate. Previously when the app was build in Xcode 15.4, it run/launch perfectly, but it seems the app is crash below iOS 15.5 ---- HERE THE CRASH LOG ------ Incident Identifier: 6E80706A-C8FA-4E6F-8F14-5746E6CA5129 Hardware Model: iPhone13,3 Process: Runner [79635] Path: /private/var/containers/Bundle/Application/ED368AA9-3A69-45CE-89CA-438440BB8781/Runner.app/Runner Identifier: - Version: 1.0.7 (3273) AppStoreTools: 16B39 AppVariant: 1:iPhone13,3:15 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: - [872] Date/Time: 2024-10-29 08:56:13.5458 +0700 Launch Time: 2024-10-29 08:56:13.4479 +0700 OS Version: iPhone OS 15.5 (19F77) Release Type: User Baseband Version: 2.54.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD 4 Symbol missing Symbol not found: _objc_claimAutoreleasedReturnValue Referenced from: /Volumes/VOLUME/*/Runner.app/Frameworks/KSCrashCore.framework/KSCrashCore Expected in: /usr/lib/libobjc.A.dylib (terminated at launch; ignore backtrace) Triggered by Thread: 0 Thread 0 Crashed: 0 dyld 0x00000001025007a0 __abort_with_payload + 8 (:-1) 1 dyld 0x0000000102506388 abort_with_payload_wrapper_internal + 104 (terminate_with_reason.c:102) 2 dyld 0x00000001025063bc abort_with_payload + 16 (terminate_with_reason.c:124) 3 dyld 0x00000001024d6828 dyld4::halt(char const*) + 328 (DyldProcessConfig.cpp:2067) 4 dyld 0x00000001024d3960 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3560 (dyldMain.cpp:0) 5 dyld 0x00000001024d1cc4 start + 488 (dyldMain.cpp:864) Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000006 x1: 0x0000000000000004 x2: 0x000000016eee1690 x3: 0x00000000000000d8 x4: 0x000000016eee1290 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000016eee0cd0 x8: 0x0000000000000020 x9: 0x0000000000000009 x10: 0x0000000000000001 x11: 0x000000000000000a x12: 0x0000000000000000 x13: 0x0000000000000037 x14: 0x00000002301c9625 x15: 0x0000000000000002 x16: 0x0000000000000209 x17: 0x00000001024fae54 x18: 0x0000000000000000 x19: 0x0000000000000000 x20: 0x000000016eee1290 x21: 0x00000000000000d8 x22: 0x000000016eee1690 x23: 0x0000000000000004 x24: 0x0000000000000006 x25: 0x000000016eee3728 x26: 0x0000000000000001 x27: 0x000000016eee3590 x28: 0x0000000000000000 fp: 0x000000016eee1260 lr: 0x0000000102506388 sp: 0x000000016eee1220 pc: 0x00000001025007a0 cpsr: 0x1000 esr: 0x56000080 Address size fault Binary Images: 0x1024b8000 - 0x10250ffff dyld arm64e <7c9c7851823738a7b1eb9cd2deb4b746> /usr/lib/dyld EOF