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?

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.

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.

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.

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 -> Organizer -> 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?

I can't use the app because I haven't received any email and I don't know what the invitation code is. Will I receive it at some point or how can I receive it?

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?

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!

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>```

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.

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.

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.

I am unable to add an individual tester to a build. When I attempt to submit the information, the test information is rejected because the phone number is invalid. Only numbers are allowed, the field is set to 03453131234, in fact any combination of digits is rejected,

Hi everyone, I built a new app and pushed it to the Testflight but call/sms is not working. Doesn't Testflight support call/sms feature?

I see the app in TestFlight. I press install, after a while the circular icon appears fills for a while and then stops and goes right back to install. How can I install an Apple Watch only app from TestFlight? I have restarted both iPhone and watch. Same thing.

TestFlight has suddenly stopped distributing new builds to internal testers. I can't even manually add those groups the latest builds.

Hi Everyone, Over the last week, some of the dev team has suddenly lost access to our test flight builds. Stating "builds expired", we've tried a few things including: removing the users from both test flight and apple connect reinstall the apps after the entire process, they're still stuck with the same "build expired" prompt. Originally only two devs were having this issue but more have started to follow. Has anyone seen something similar before? Thanks,

Hello, We're attempting to validate our application archive through Xcode but the application is crashing during the validate step and we're not sure why. Platform: macOS 15.1 Arch: arm64 We've confirmed that our developer agreements are up to date (a suggestion made by other posts on these forums). Other suggestions have been to downgrade Xcode but we're hoping there's another explanation. The application is quite complex - many libraries and framework - but executes as expected during development and testing. Crash Report Any insight into this error would be appreciated. We're sure it's something wrong with our plist or archive structure but the crash is limiting our ability to debug.

I submitted an appeal (Appeal Ticket: APL122726), Apple App Review Team responded (24.02) that my demo account does not work (not available to check the application) and asked for restoring it. Demo account was restored by me 10 hours later. I notified App Review Team about it. But I didn't get any response. I can't get any response for one week. The continued suspension of our app is having a significant impact on our business and our users. Specifically the app's unavailability continues to result in a substantial loss of revenue. Please, review my appeal. Thank you.

I want to create test flight for my unity project. But every time I create test flight for internal testing its say couldn't install your app. Please help