We have noticed that the hang reports provided in Xcode include the percentage of hang time, which are used to sort from high to low (effectively sorting by priority). However when adding these percentages up we do not get 100%. For newer releases the total may be quite low (5-20%) but even for older releases we only get up to around 85%. Are there reports we are missing? Is there a threshold or something that lower percentage reports are not hitting? Any level of understanding here would be appreciated!

I'm receiving reports from users that my app is crashing immediately after being opened on the Apple Watch Series 10 using watchOS 11. I've updated my personal Apple Watch Series 8 to watchOS 11 and I'm unable to reproduce this crash using the same release build from the App Store. The version currently on the App Store was built using Xcode 15.4 (22622). I'm preparing an update that is built using Xcode 16.0 (23051) and have asked one of the users reporting the crash to try a TestFlight build built using Xcode 16.0 and they are no longer experiencing this crash. As far as I can tell, the only difference between the version on the App Store and the TestFlight build is that it is built with the watchOS 11 SDK included with Xcode 16.0. I don't think any of my app's dependencies (all managed by Swift Package Manager) have been updated in the TestFlight build. I'm attaching a crash report submitted by one of the users. I believe this is a partially symbolicated crash report and have tried opening it in Xcode in an attempt to make it fully symbolicated without success. I've also received a video recording of the app crashing. I'm also not able to see any crashes occurring with an Apple Watch Series 10 in the Xcode Organizer, which leads me to believe this crash may be occurring at the Springboard level. Any help to further diagnose this issue would be much appreciated.

Hello everyone, I’m encountering an issue while trying to archive my app in Xcode, and I hope someone can help me troubleshoot it. Error Details: Domain: IDEArchivedApplicationErrorDomain Code: 1 Failure Reason: Archive content at path /Users/c1/Library/Developer/Xcode/Archives/2024-09-22/alpha release 4 22-09-24, 2.52 PM.xcarchive/Products/Applications/Runner.app is missing a bundle identifier. User Info: DVTErrorCreationDateKey = "2024-09-22 09:22:03 +0000"; Steps Taken: I’ve verified that the Bundle Identifier is correctly set in the project settings under the General tab. Cleaned the build folder (Product > Clean Build Folder). Restarted Xcode and attempted to archive again. Checked that all targets in the project have a valid Bundle Identifier. Has anyone experienced a similar issue or have any suggestions for resolving this? I would appreciate any guidance on how to fix this missing bundle identifier error. Thanks in advance for your help!

XCode version: Version 16.0 (16A242d) macOS: 14.6.1 (23G93) Hi, I'm getting this error while uploading my app using XCode 16. I just updated XCode from 15 to 16. On XCode 15 it worked fine when I uploaded apps, no error no warnings, but on XCode 16 there are list of warnings for OneSignal framwork. Here is one of the error, and the others are all the same (OneSignal has multiple packages). Upload Symbols Failed The archive did not include a dSYM for the OneSignalUser.framework with the UUIDs [***]. Ensure that the archive's dSYM folder includes a DWARF file for OneSignalUser.framework with the expected UUIDs. My Podfile looks like this: target 'my_target' do # other packages pod 'OneSignal/OneSignal', '>= 5.0.0', '< 6.0' pod 'OneSignal/OneSignalInAppMessages', '>= 5.0.0', '< 6.0' end target 'OneSignalNotificationServiceExtension' do pod 'OneSignal/OneSignal', '>= 5.0.0', '< 6.0' pod 'OneSignal/OneSignalInAppMessages', '>= 5.0.0', '< 6.0' end OneSignal uses vendored frameworks, and I don't believe they provided the symbol files. Will this affect my app in any way? How can I resolve this issue?

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 !

H! I was invited to App Store Connect (personal account). But when I try to archive app in Xcode it says that my team does not support it. Any fix?

H! I was invited to App Store Connect (personal account). But when I try to archive app in Xcode it says that my team does not support it. Any fix?

Hi, we have an iOS VPN app that uses NEPacketTunnelProvider. One of the Metrics that we track in XCode Organizer is Battery Usage (On-Screen Battery Usage, Background Battery Usage). Could you clarify: Does Battery Usage statistics in XCode combine app's and active tunnel's battery usage or just the app's battery usage? When the app is not active and not in background, but VPN tunnel is active, does this reflect in Battery Usage statistics per app versions?

The "Last Day" filter in the crashes section of the Xcode Organizer, never has any crashes in it. If we use the "Last Two Weeks" filter, then you can clearly see that we do have crashes every day. They even show crashes for yesterday in the little graph in the "statistics" window. So why dont they show up in the last day filter? Is there some hidden setting we don't have enabled? This also seems related to the fact that the number of crashes from "yesterday" is always incomplete. i.e. waiting another day makes the number go up, implying not all crashes were included in the original number. This means we have to wait two days to get the data from one day ago. Why?

If a crash get's marked as "Resolved" in Xcode organizer: Will it automatically get reopened if the same issue occurs again in a new/ later app version? If yes: Where is this documented?

Hi, my Xcode is crashing immediately after clicking on 'Distribute' (after selecting 'Distribution Method', and regardless of the method I choose). I've tried: Updated Xcode Cleared Derived Data Updated macOS Created new signing certificates After all changes I created new archives but had the same result on distribute. I recently cleaned up my mac, so I suspect I might've deleted something important. My touch bar also recently broke. Other than that, I can't think of any other variables since my last successful distribution attempt. Please help, I've never experienced any issues like this. I've attached snippets from the report as a text file, but the full report was too large: xcode_crash_report.txt

Crash reports in Xcode Organizer are only partially symbolicated. Frames for the OS are symbolicated but the app is not. I've followed the guidance here but app frames are still not symbolicated. https://forums.developer.apple.com/forums/thread/690094 We archive, export ipa and upload our iOS app using the command line instead of with Xcode UI. Archive xcodebuild -project myproject.xcodeproj -scheme myproject -archivePath build/myproject_results.xcarchive archive Export IPA xcodebuild -exportArchive -archivePath build/myproject_results.xcarchive -exportPath ./build/ipa/ -exportOptionsPlist /path/to/ExportOptions.plist In ExportOptions.plist we set uploadSymbols to true <key>uploadSymbols</key> <true/> Upload xcrun altool --upload-app -t ios -f $ipa_path -u $appstore_connect_username -p $appstore_connect_password When inspecting the .ipa file, I see .symbols files in the Symbols folder. I verified that the UUID from our dSYM matches one of the UUID .symbols files as well. How would I fix or further debug this issue?

Hello, We encountered the following error while attempting to upload our visionOS app. Please note that this is not an iOS app; we have specifically built the framework for the arm64 visionOS platform. Incorrect Platform. You included arm64 executable “XX.app/Frameworks/XX” in your iOS bundle. Only iOS executables can be included.

Our iOS app also has a Safari Extension and a Packet Tunnel Extension. When trying to gather crash logs from the packet tunnel extension, we get an error like: ***@***[dot]com failed with error: Access Restricted. Even the account holder account was unable to access these crash logs. Is there any access level that does allow access, or are they restricted in all cases for all permission levels?

I have a multiplatform app with a single target. I’ve been focused on making release updates for just visionOS where the new version doesn’t really have any changes to the iOS/iPadOS content. When I build and archive a new version and build number for my single app target, is it an ok practice to only release the new version and build to visionOS and not iOS? The reason I ask, is that the next time I get around to releasing a version and build that has any iOS changes that I want to release on the iOS App Store, it will have skipped one or more version numbers (due to only visionOS releases) from the last time that version was seen on the iOS App Store because I was only doing visionOS releases and versions prior to that.

Hello there. I'm having trouble with notarization in Xcode. I'm developing a Swift Mac app with Xcode 14, but even when I enable Hardened Runtime and perform notarization, it displays the message "Hardened Runtime is not enabled" and I can't proceed. The steps for notarization are [Window] -> [Organizer] -> [Distribute App] -> [Developer ID] [Next] -> [Upload]. Could you please tell me what I should check, or any other information? I've attached screenshots. Thank you.

When I do an archive build of my app against visionOS, the archive listing in the Organizer show the archive entry as iOS. So I have one archive build for iOS with a certain build number and another archive build for visionOS with another build number (incremented by 1) They are both listed in The Organizer but they both have iOS info. I’ve submitted them both separately to TestFlight and I’m about to try to test it on visionOS. Shouldn’t the visionOS archive build that I submit to TestFlight indicate something about visionOS instead of iOS?

No metrics data found for the latest app versions with sufficient usage. What is sufficient usage ? Can we define sufficient usage ourself ? if Yes then how ? https://developer.apple.com/videos/play/wwdc2020/10076/ wwwdc200 does mention factor of 5, but 5 of what ? and when where is the definition ? Organizer -> Metrics is useless if there is no data. If someone knows the fix please suggest.

Archive a package. [Window] -&gt; [Organizer] -&gt; select package just archived -&gt; click [Distribute App] select [App Store Connect] -&gt; click [Distribute] -&gt; CRASH! crash log Process: Xcode [12835] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497799835 App External ID: 863955376 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-04-15 11:05:05.6599 +0800 OS Version: macOS 14.4.1 (23E224) Report Version: 12 Anonymous UUID: E74ED973-D26C-0B5C-FDB1-837215F4F6B9 Sleep/Wake UUID: 6627EBDD-D3B7-4988-B9E5-BEDB5E1ED228 Time Awake Since Boot: 92000 seconds Time Since Wake: 11424 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [12835] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x194e6aa60 __pthread_kill + 8 1 libsystem_pthread.dylib 0x194ea2c20 pthread_kill + 288 2 libsystem_c.dylib 0x194dafa20 abort + 180 3 libswiftCore.dylib 0x1a4f049f4 swift::fatalErrorv(unsigned int, char const*, char*) + 128 4 libswiftCore.dylib 0x1a4f04a14 swift::fatalError(unsigned int, char const*, ...) + 32 5 libswiftCore.dylib 0x1a4f04be0 swift::swift_abortRetainUnowned(void const*) + 48 6 libswiftCore.dylib 0x1a4f08f10 swift_unownedRetainStrong + 140 7 SwiftUI 0x1c1cea47c 0x1c075f000 + 22590588 8 SwiftUI 0x1c1cea42c 0x1c075f000 + 22590508 9 AppKit 0x198c517d4 -[_NSQuickActionAutovalidationScheduler windowDidUpdate:] + 140 10 CoreFoundation 0x194f76b1c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 11 CoreFoundation 0x19500adb8 ___CFXRegistrationPost_block_invoke + 88 12 CoreFoundation 0x19500ad00 _CFXRegistrationPost + 440 13 CoreFoundation 0x194f45648 _CFXNotificationPost + 768 14 Foundation 0x196061464 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 15 CoreFoundation 0x194fadd4c -[NSArray makeObjectsPerformSelector:] + 212 16 AppKit 0x1987dccb4 -[NSApplication(NSWindowCache) _updateWindowsUsingCache] + 108 17 AppKit 0x1987dcc0c -[NSApplication updateWindows] + 64 18 AppKit 0x198c19a3c __38-[NSApplication setWindowsNeedUpdate:]_block_invoke_2 + 56 19 AppKit 0x198c1eb6c ___NSRunLoopObserverCreateWithHandler_block_invoke + 64 20 CoreFoundation 0x194f81254 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 21 CoreFoundation 0x194f81140 __CFRunLoopDoObservers + 536 22 CoreFoundation 0x194f8076c __CFRunLoopRun + 776 23 CoreFoundation 0x194f7fe0c CFRunLoopRunSpecific + 608 24 HIToolbox 0x19f71b000 RunCurrentEventLoopInMode + 292 25 HIToolbox 0x19f71ac90 ReceiveNextEventCommon + 220 26 HIToolbox 0x19f71ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 27 AppKit 0x1987d8970 _DPSNextEvent + 660 28 AppKit 0x198fcadec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 29 DVTKit 0x10313f858 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 30 AppKit 0x1987cbcb8 -[NSApplication run] + 476 31 DVTKit 0x10313eb24 -[DVTApplication run] + 60 32 AppKit 0x1987a2f54 NSApplicationMain + 880 33 dyld 0x194b1a0e0 start + 2360

Hello fellow developers, I've encountered a code signing issue during the archiving process in Xcode and I'm looking for some guidance. Here's the error message I received: codesign command failed (/var/folders/44/968_7v_972vb03blw9l1_sqr0000gn/T/XcodeDistPipeline.~~~k4kX6H/Root/Payload/SweetifyCrm.app/Frameworks/hermes.framework: replacing existing signature /var/folders/44/968_7v_972vb03blw9l1_sqr0000gn/T/XcodeDistPipeline.~~~k4kX6H/Root/Payload/SweetifyCrm.app/Frameworks/hermes.framework: invalid or corrupted code requirement(s) Requirement syntax error(s): line 1:140: unexpected token: SWEETIFY ) Here's what I've tried so far: Cleaned the build folder and rebuilt the archive. Ensured that the correct signing certificate and provisioning profile are in use. Checked .entitlements file for any syntax errors or misplaced tokens. Searched for the token "SWEETIFY" in my project, which is part of the development team name, but didn't find any irregularities. This error seems to be triggered when codesign is executed during the archiving process, specifically with the Hermes framework which is part of my React Native project. I'm using Xcode version 15.0.1, and my project includes Hermes as a JavaScript engine. The issue arises when I try to archive the app for distribution. The word "SWEETIFY" appears to be causing trouble, but it's merely part of the development team's name, (LLC "SWEETIFY"). Has anyone faced a similar issue or could offer some insight into what might be going wrong here? Any help or suggestions would be greatly appreciated! Thank you in advance for your time and help.