Good day, I've uploaded a build to TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our project started in Objective-C and have mixed swift class and pods. The last uploaded build without any automated response was Nov 8, 2023. I'm using XCode Version 26.0.1 (17A400). I've tried every way i found in internet and i'm not able to find any solution for this. ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES use_frameworks! :linkage => :dynamic (in pods) We would appreciate any assistance in clarifying why this issue is occurring and how we should proceed to address it. Your guidance would mean a lot. Thank you.

I've been trying to send an archive with Organizer to iTunes Connect. It's not my first time. I've been doing it for more than a decade. Anyway, when I try to send a package for my new macOS application, Organizer gives me two error messages that I have never seen before. App Record Creation Error App Record Creation failed due to an invalid attribute. The SKU you entered has already been used. App Record Creation Error App Record Creation failed due to request containing an attribute already in use. The app name you entered is already being used for another app in your account. If you would like to use the name for this app you will need to submit an update to your other app to change the name, or remove it from App Store Connect. An odd thing is that, as shown in the screenshot below, Organizer demands that I enter an application name and SKU manually. I've entered the exactly same ones from the App Store Connect page. I didn't see this step on Organizer last month. I'm using a new SKU for this submission. And I don't have an existing application at iTunes Connect with the same application name. I guess it's the same issue that has been reported here.. I have no pending contract issues. How do I send an archive without errors? My Xcode version is Version 16.4 (16F6). Thanks.

Trying to upload an iOS26 app archive with Xcode 26 beta 7 and getting ITMS-90717: Invalid large app icon, meaning my app is not eligible for TestFlight testing. My App contains an IconComposer .icon asset, so I'm not sure what it's complaining about. I'm not seeing anything in the release notes about this, and I'm not sure if I'm doing something wrong or not.

I am using GoogleMobileAds package dependencies and now when I want to archive and export an app I get this two warnings : Upload Symbols Failed The archive did not include a dSYM for the GoogleMobileAds.framework with the UUIDs [13B55A37-D103-36E1-8D7B-FA4EAB2C8146]. Ensure that the archive's dSYM folder includes a DWARF file for GoogleMobileAds.framework with the expected UUIDs. Upload Symbols Failed The archive did not include a dSYM for the UserMessagingPlatform.framework with the UUIDs [A3941120-02A1-30B5-8C28-BFC0F9496E16]. Ensure that the archive's dSYM folder includes a DWARF file for UserMessagingPlatform.framework with the expected UUIDs. I have updated the packages to 11.9.0 (lasted) and Xcode 16 to 16 RC (lasted also) and I would like to know how to fix this... With Xcode 15 I have no problem !! I can export with no warnings ! But now with Xcode 16 no... Thanks for helping !

Hello , am facing issue in submitting my app to store I have submitted my case to apple developer team my case ids "101969263018","101975805043". they told me to submit the report from feedback assistance my case id : FB12141270. but still I don't get any replay form feedback assistance. after that I submitted my case to DTS engineer case id : 2394373. got email to submit some file which I have submitted after that still I don't get any reply from DTS team. please help me to short out this issue. last one month am trying to short out this issue with apple developer team. still I don't get solution.

I am writing to report a critical issue with the Xcode Organizer. It is failing to download App Version Information from App Store Connect, which prevents our team from accessing vital performance reports like disk writes, hangs, and launches. Other features such as Crashes, Metric's items work fine. When I open the "Reports" tab in the Xcode Organizer, it consistently shows the following error: Xcode failed to load builds for "{Service}". "{Account}" failed with error: No Versions. [Important Context] What is particularly concerning is that this functionality used to work correctly. We were able to see build versions and access their reports up until a certain build in the past. However, at some point, this stopped working, and now no versions are loaded. Given that I am an Admin and this feature was previously working, the issue does not appear to be a simple permissions problem. It seems a change has occurred, either on the server-side or in how Xcode interacts with our app's record on App Store Connect. Could you please help us understand: What might have caused this sudden change that prevents build versions from being loaded? What steps can we take to resolve this "No Versions" error and restore access to our performance reports? Thank you for your investigation into this matter.

Two month back we published 28.11.0 version a app. for both foreground and background terminations are not properly showing by Xcode matrix Foreground Termination: I was able to see the termination bar chart for one release, but after that, the chart stopped showing real-time crash progress. However, crashes are still being reported directly by users. Why is Xcode Organizer unable to capture these events? Please help us track them effectively. Background Termination: The termination bar chart has not appeared in Xcode Organizer for the last two releases, which span nearly two months. As a result, we are unable to monitor app terminations for background scenarios.

Hi everyone, I’m currently unable to view crash logs in Xcode Organizer for any of the apps in my account. When I try to access crash reports, I receive the following error: "An error occurred preventing Xcode from downloading version information from App Store Connect. An unexpected error occurred: [<__NSDictionaryM> valueForUndefinedKey:]: this class is not key value coding-compliant for the key [App Name] [Version] (iOS App)." The error message references an app name and version that were previously used. Notably, the original app name included an @ symbol (e.g., @ExampleApp). We suspected this might be contributing to the issue, so we updated the app name to remove the symbol. However, the error persists and still references the old name. Has anyone experienced something similar or found a workaround? Any guidance would be greatly appreciated! Thanks in advance.

Got emailed three .txt crash files. Cannot for the life of me figure out how to get Xcode to do something with them. Tried: renaming .txt to .crash Dropping onto "devices and simulators" window Dropping on to "devices and simulators > select device > View device logs" "Download debug symbols" for the archive in Xcode (says "dowloaded debug symbols" so did it) ... and many other things Xcode 13 simply refuses to respond to the drag-and-drop of the file no matter the file extension and no matter where in Xcode's various windows/tools I drop it. Has anyone done this with a crash .txt file from app review and Xcode 13?

I create a help book for my macOS app and it works locally. However, when I try to upload the app to App Store Connect I get a strange error: Image: Text: Bad CFBundleExecutable. Cannot find executable file that matches the value of CFBundleExecutable in the nested bundle DottieHelp [com.gingerbeardman.Dottie.pkg/Payload/Dottie.app/Contents/Resources/DottieHelp.help] property list file. (ID: 48052567-91cc-43ca-8d7c-0f14bd60e6da) This is curious, because there is no executable in the help file. If I delete CFBundleExecutable from the help target in Xcode, it keeps coming back. Why? But if I do an Archive build, then go deep into the bundle and manually remove entry for CFBundleExecutable then the build uploads fine. Any ideas how I can prevent Xcode from adding CFBundleExecutable key to the info.plist of a help file? macOS 14.7.6 (23H626) Xcode 16.2 (16C5032a)

Dear Experts, What is the current best practice for build numbering? I ask because I am aware that when exporting an archived app for upload I am now asked if I want Xcode to manage the build number for me. In the past I have set a build number in the Info.plist, often based on the date, e.g. 2.4.20230218. Now, I am asked if I want that to be replaced by something like 2.4.7 (if I recall correctly). So far I've answered No. Previously I have searched for automatic build numbering and I've found web pages that suggest adding a script to the build process that automatically increments the build number in the info.plist, or similar. I've not tried to implement that myself. In some of my apps, I have code that needs to know the full version at compile time (e.g. app receipt validation). How would that interact with the new feature? Thanks, Phil.

We've seen a recent increase in background terminations: blue - System Pressure orange - Task Timeout I'm trying to understand the increase in system-pressure terminations, since there's no corresponding increase in memory at suspension. Are there other system resources for which iOS will terminate an app?

I have an iOS app and that has CarPlay enabled. I have Siri capability and the feature has been tested in Car. The voice commands are working perfectly fine. However, I am facing a weird issue as described below, The key NSSiriUsageDescription, is set to custom text in info.plist. After generating archive, I exported and checked the package contents, in which the the key NSSiriUsageDescription was reset to default text(Describe why your app needs Siri access) in the info.plist. I do not have any dynamic build process that's writing to the info.plist. Only the Siri key is being reset, rest of keys like camera/location permissions are intact. Kindly suggest what needs to be done at my end

Hi everyone, I'm working on an iOS app developed with React Native (version 0.69.4), and I'm running into an issue when trying to upload the archive to App Store Connect. My app is designed to work only in landscape orientation, so in Xcode I’ve set the supported interface orientations accordingly—only landscape left and landscape right are checked, and portrait options are unchecked. However, when I try to upload the build to App Store Connect, I receive an error indicating that the app must support the portrait orientation on iPhone. The upload process is being blocked due to this setting. For the functionality and layout of the app, supporting portrait mode is not ideal. Is there any recommended way to configure an app so that it can still be uploaded successfully while supporting only landscape orientation on iPhones? Any advice or workarounds would be greatly appreciated. Thanks in advance!

why my Xcode organizer can not show Hangs

I want to archive app, but can't choost appstore or other release method.

After uploading the app archive generated by Xcode (which passed validation), I received an email stating one or more files had the com.apple.quarantine extended file attribute and to remove the attribute before uploading the archive again. A particular PNG file was identified. In the terminal, I ran the command: xattr -d com.apple.quarantine The response was: "No such xattr: com.apple.quarantine" I also ran "xattr -rd" on the directory containing all app files. No response. The identifed PNG file at fault is a screenshot used only in the app's User Guide. It was created 5 years ago using Apple software: Ctrl-Shift-4 to capture the image, Preview to resize. Given the file does not have the quarantine extended attribute, I can only conclude that Xcode is adding the attribute when building the archive. How do I stop Xcode from adding the attribute? I have search Google with numerous search criteria and check the Apple Developer Forum, but could only find how to remove the attribute using xattr; nothing about Xcode adding the attribute when building an archive.

Hello, I archive my macOS app and Xcode can create it successfully, however when I validate the archive there are 2 errors: Cloud signing permission error (You haven't been given access to cloud-managed distribution certificates. Please contact ...). No profiles for 'my app-bundle-identifier' were found (Xcode couldn't find any Mac App Store provisioning profiles matching 'my app-bundle-identifier'.). I have added my Apple ID account in Xcode and enable "Automatically manage signing" option for signing my app target, and Xcode can build the target successfully without any problem with certificates or provisioning profiles when archive. I have some components (frameworks, daemon, xpc services, share extension) which are put in Frameworks, Resources, XPCServices, PlugIns folders in app's Content, and use post build script to manually code sign for all of these components by ${CODE_SIGN_IDENTITY}, and Xcode can sign those components without any problems when building for archive. I already created Mac App Distribution and Mac Installer Distribution, and macOS App Store profile for my app-bundle-identifier. I don't understand why Xcode still reports the error regarding Mac App Store provisioning profiles when I validate the archive and can't figure out how to fix the issue because I have enabled "Automatically manage signing" so that Xcode can automatically select the appropriate profiles when it archives the app. Any suggestion for how to fix the issue?

Xcode 16.2 archive fails to compile XIB Xcode Archive command fails most of the time while compiling an XIB which was created in older Xcode. XIB was updated in Xcode 16.2 version also which did not fix this issue. Archive from Xcode app works but Xcode build command fails and no reason shown by the command. ** ARCHIVE FAILED ** The following build commands failed: CompileXIB /Users…/Resources/Nibs/<XIB_NAME>.xib

Hello, For one of my recent release (2 versions ago), I used to be able to check its p50 of Hang Rate, but now it disappear and not showing up in XCode Organizer Metrics anymore. The p90 of Hang Rate of this version is still there. It's so unpredictable. Is there something we can do to get this data to populate? If not, may I understand usually why this issue will happen, is it something frond-end bug or is it because there is some thing abnormal going on in the back-end data?