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?

I have a very annoying problem when I try to distribute my app to the App Store. Organizer does not recognise the project as an app I think. Xcode version is 16.2 but I have tries in 15.4.

If an iOS app gets terminated by watchdog due to, for example, hanging the main thread, is that considered to be a crash or something different. I'm asking because, according to google and AI, Crashlytics can detect and report these,but in my experience it does not. If I deliberately cause a watchdog termination by for example sleeping on the main thread for a long time then these never appear in Crashlytics. I know Apple folks here don't comment on non Apple software, so I'm not asking about Crashlytics, just wondering and interested about watchdog timeout terminations and how they differ from a "regular" crash.

I've been trying to upload my app to the App Store with Xcode 16.3 RC but I keep getting these error messages. When will Apple start allowing Xcode 16.3 submissions?

We recently integrated MetricKit into our app; however, the 90th percentile data does not seem to match the data in Xcode Organizer. The values reported by MetricKit appear to be higher. Additionally, it looks like data for previous app versions is not being updated in Organizer as adoption of the latest version increases. Has anyone else experienced this issue? Could there be a delay in data updates for older versions in Organizer? Are there any known limitations or best practices for ensuring consistency between MetricKit and Xcode Organizer data? Any guidance would be greatly appreciated.

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?

Hi there - when attempting to upload the latest build of my macOS app to App Store Connect via Xcode's Organizer I'm now greeted with this warning. I don't even know what it's attempting to tell me.. Yes, I understand what dSYMs are for - but the UUIDs don't appear anywhere in my workspace (full text search on the folder), in the build log, or the ..thing.. the 'Export' button generates. Any help much appreciated, ATM I don't even know where to start. Cheers, Jay

I can’t view energy reports in the Xcode Organizer. I keep getting the message “An error occurred while downloading energy reports. Please provide a valid value” Feedback ID: FB16595567

Our team is currently handling hang issues and logs received by the Organizer during our project. Regarding the xCode Organizer, we’d like to ask a few questions: The hang rate is presented as a bar chart for each app version. Is there any way to get detailed information for each versions? For example, what percentage of the hang rate is attributed to users on different iOS versions? We've encountered a situation where the hang logs have decreased, but the hang rate has increased. Could you explain why this might occur? I was wondering how the hang rate is sampled. For instance, does it record all users who experience a hang, or only those under specific conditions? The situation is that we can see only a handful of hang logs (around 13), but we have hundreds of thousands of DAUs. This ratio seems quite off. Could you explain what might cause us to receive such a small number of logs for each version?

Hi there, our team is facing a problem distributing our app archive to TestFlight. When we try to do so through the Product &gt; Archive option, we get a generic Xcode Archive error message, stating that we can’t distribute or validate it. This issue has been persistent for a few days now, and we’ve been unable to resolve it. We’ve reviewed the documentation (e.g., TN3110, TN3109) to ensure that we’ve set the “Skip Install” option to “No” and the Installation Directory to $(LOCAL_APPS_DIR). However, these changes haven’t made any difference. Another complication is that we’re using our team member’s developer account to distribute the app. As a result, we’ve encountered code signing issues with their credentials on our own devices. Despite our efforts, we’ve been unable to log in to their account. We would greatly appreciate any assistance you can provide in resolving this issue. Thank you for your attention to this matter.

Update Xcode 16.2 but i get error Assets Validation Failed upload to Appstore,

I am currently investigating an issue with my app's slow launch time in Xcode 16. However, when I open the Launches pane in the Xcode Organizer, I can only see the report list, but I encounter an error message like the one below in the stack trace. This issue also occurs in the Disk Writes, Energy, and Hangs panes, but not in the Crashes pane. Can someone advise me on what steps I should take? Any help would be greatly appreciated.

I have a problem uploading to testflight. When I archived my app, it announced success, but when I went to the appstoreconnect website I didn't see any builds, while I waited a long time for it to be pushed up. And one more problem, when the upload notification is uploaded, after a while there is a notification that my app for ios is not a valid binary, I don't understand this problem. Can you please ask me how to solve it?