TestFlight

RSS for tag

TestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.

Posts under TestFlight tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

Call Tracking with CallKit Works in Debug Mode but Not in Release (TestFlight) – iOS
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
0
0
27
2w
I uploaded the app to TestFlight, but the new version doesn’t appear in the TestFlight app.
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!
5
6
218
2w
TestFlight 3.8.0 crashes on launch on iOS 14.1
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
1
0
171
2w
Xcode crash reports from TestFlight
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?
0
0
25
3w
Which option to choose for TestFlight application feedback in the Feedback application?
As I've more verbosely asked at apple.stackexchange.com/revisions/479121/1#:~:text=Screenshot-,Screenshot,-I%20am%20able, when reporting feedback for an application installed via TestFlight, which of Feedback Assistant's "Third-Party Apps"'s "Something else not on this list" or "TestFlight" categories are superior? I ask primarily because applications installed via TestFlight are not enumerated there. However, also because via Feedback Assistant, I can provide significantly better feedback than I can on TestFlight, because of its undermentioned attributes: I can provide follow-up information as I gain more, and correct old information. It provides draft functionality, in case I need to take some time to create an actionable report. I can upload more information, like multiple screenshots and other file types.
4
0
49
3w
Xcode 16 Supports iOS 12 Deployment Despite Official iOS 13 Minimum - Will This Continue?
I've noticed that despite Apple stating Xcode 16's minimum deployment target is iOS 13, I was able to set my app's minimum target to iOS 12, build it, and successfully upload it to TestFlight. I've tested the app on iOS 12 devices, and it functions normally. Given that updating to Xcode 16 will be mandatory after April 24th, I have a few questions: Is it intentional that Xcode 16 still allows targeting iOS 12? Will Apple continue to support this capability for iOS 12 devices in the future? Are there any plans to restrict or block apps targeting iOS 12 in upcoming Xcode updates? I'm seeking clarification on whether it's safe to continue supporting iOS 12 in our apps or if we should prepare for potential changes. Any insights from the Apple development team would be greatly appreciated.
1
0
58
3w
Failed to Add Testers to TestFlight Build with Status "409"
Our test application has the status "Approved" on the test build list view. However, when adding testers to the test build, the process failed with the error message "An error has occurred. Try again later." **Here is the API request: ** https://appstoreconnect.apple.com/iris/v1/builds/d9bc89fa-e94d-4a33-a39c-20550c0673ec/relationships/individualTesters Here is the response: { "errors" : [ { "id" : "5b833be8-18d1-4ce9-b47d-7a315ef49a50", "status" : "409", "code" : "STATE_ERROR", "title" : "The request cannot be fulfilled because of the state of another resource.", "detail" : "Tester(s) cannot be assigned" } ] } Does anyone experience the same issue? Any insight on the root cause? I am wondering if this could be fixed by itself. Any input and help is appreciated.
1
0
55
3w
buildAudienceType is not working as expected
Hi, Am using fastlane to upload into TestFlight. Am able to successfully upload the build without any issues. For Testing Internally , I want to upload the build into App Store Connect but I should restrict it on submitting to App Store. ( This is possible when i distribute the app via TestFlight Internal Only from XCode -&gt; Organizer -&gt; Distribute App (Select option with TestFlight Internal Only). I want to achieve the same using either Transporter/ fastlane. I tried setting buildAudienceType to INTERNAL_ONLY as per https://developer.apple.com/documentation/appstoreconnectapi/buildaudiencetype but it is not working. Can you suggest how i can achieve this via fastlane?
0
0
146
3w
My Xcode-submitted app isn't appearing in the builds listing on the Connect site, suddenly
I've been uploading my app (Find Any File) to the App Store since its very first day, around 2010. It always worked. But now, after I the last successful release at the beginning of January, I am not able to get my app into the Store any more. Xcode 16.2 reports that it successfully uploaded my app, without warnings. Yet, it never appears in Connect's TestFlight builds. I just keep seeing this for the new version (2.5.6): And, after a while (less an hour), that entire 2.5.6 section disappears again as if there had never been an upload for 2.5.6. I don't get any emails about the submission or about an issue with it, either. It's like my submissions are suddenly blocked by Apple. Now I cannot submit a new version any more. What's going on there? I anyone else having a similar issue?
1
0
136
4d
TestFlight Not Working – "TestFlight Unavailable" on iPhone 15
I'm having trouble launching TestFlight on my iPhone 15. As soon as I open the app, I see the welcome screen, but then I immediately get the following error message: TestFlight Unavailable TestFlight is temporarily unavailable. Try again. I can't proceed further – after tapping "OK," the message disappears, but TestFlight remains unusable. I've tried: Restarting my iPhone Uninstalling and reinstalling TestFlight Checking my internet connection (both Wi-Fi and LTE) Signing out and back into my Apple ID The issue persists. Is anyone else experiencing this? Is this a known issue on Apple's end? Attaching a screenshot for reference. Device: iPhone 15 iOs: 18 Any help would be appreciated!
1
0
122
4w
App Store Connect Build Upload Failing – Gateway Timeout (504)
App Store Connect Build Upload Failing – Gateway Timeout (504) 🔄 I’m trying to upload a build to App Store Connect through Xcode, but the process keeps failing with a Gateway Timeout (504) error. It looks like Apple’s API or App Store Connect is receiving an invalid response from an upstream service. The server returned unexpected content. <!DOCTYPE html> <html lang="en"> <head> <style> body { font-family: "Helvetica Neue", "HelveticaNeue", Helvetica, Arial, sans-serif; font-size: 15px; font-weight: 200; line-height: 20px; color: #4c4c4c; text-align: center; } .section { margin-top: 50px; } </style> </head> <body> <div class="section"> <h1>&#63743;</h1> <h3>Gateway Timeout</h3> <p>Correlation Key: **********</p> </div> </body> </html>```
8
8
398
4w
Migrated purchases, now TestFlight will not let me rejoin betas
A few days ago I migrated my purchases from my secondary AppleID to my primary. One of the requirements was to stop testing apps in Testflight. I stopped testing in the app as directed. After the migration I am not able to rejoin my testing app. It says it is connected to my secondary ID and I need to sign in with it. The whole point of migration was to not have two IDs for iCloud and Media and Purchases. I have no intention of signing in with my other ID, it's impractical. How can I get TestFlight to relinquish the secondary ID? Developer sent a new invitation but to no avail. Deleted app and data, reinstalled, to no avail.
0
0
145
Mar ’25
HELP: App Clip Card Doesn't Appear!
I integrated an Advanced App Clip Experience to my app. In trying to test the App Clip Card, the card does not appear when I tap the link on my device that is associated to the Advanced App Clip Experience. Listed are some contextual information: Testing on device running on iOS 18.3.1 Associated Domains: Main target app: applinks: App clips target app: applinks: and appclips: Archived and uploaded build to App Store Connect. Green "Testing" status via Testflight. On Distribution tab, green "Valid" status for build domain. Advanced App Clip Experience green "Received" status. Developer App Clip Testing Diagnostics: Green "Register Advanced Experience" status Green "App Clip Code" status Warning "App Clip Published on App Store" Orange Circle "Associated Domains" After looking at countless threads, I still cannot for the life of me find a solution to test the App Clip. Any guidance would be extremely appreciated. I had also submitted a support ticket with case ID #102552504973.
11
0
349
7h
Xcode Cloud Signing Issue
There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” 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. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.
1
2
253
Mar ’25