dsym file

Your build commands have a few mistakes. I made the same simple framework you did (a single Swift struct), and used the following build commands instead. I'm going to format them here with line breaks and indentation for readability. Note that I've set Build Library for Distribution to Yes and Skip Install to No in the framework target's build settings, so they don't appear here. % xcodebuild archive -scheme StructKit -destination generic/platform=iOS -archivePath iOS.xcarchive % xcodebuild archive -scheme StructKit -destination generic/platform=iOS Simulator -archivePath sim.xcarchive % xcodebuild -create-xcframework -framework iOS.xcarchive/Products/Library/Frameworks/StructKit.framework -debug-symbols iOS.xcarchive/dSYMs/StructKit.framework.dSYM -debug-symbols iOS.xcarchive/BCSymbolMaps/<UUID>.bcsymbolmap -framework sim.xcarchive/Products/Library/Frameworks/StructKit.framework -debug-symbols sim.xcarchive/dSYMs/StructKit.framework.dSYM -output StructKit.xcframework I also notice you

tap right click on Download dSYM then type save link as ..., when you click the save button, it will show in the bottom bar in google chrome ' can't be downloaded securely' so click on arrow and tap keep, it will download successfully.

I'm facing the exact same problem.I can upload only if I uncheck Include App Symbols.....However, the archive does contain DSYMs and all build settings are correct re: symbols.This looks like a bug.

Same here 16.0 (16A242). I did not change any project settings. Also when uploading to App Store Connect it warns about Upload Symbols Failed The archive did not include a dSYM for the GoogleMobileAds.framework maybe that is related?

I'm seeing the same thing. I wonder if it's related to the new submission system. It changed recently to allow multiple submissions at the same time. This was the first build using this new system that is missing dsyms.

Thanks Ford for the reply. This is the warning: It's your choice whether or not to include symbols Im using xcodebuild command tool to generate the framework with MACH_O_TYPE=staticlib and GCC_GENERATE_DEBUGGING_SYMBOLS=YES but the dSYMs are not generated. Any help would be appreciated.

I'm sorry I don't think I understand your comment. We have uploaded our build (and many builds) to App Store Connect, and yet the download dSYM link is not present in the build metadata section of App Store Connect.

I also ran into the same issue, the thing is, just a few hours ago on the 29th of March, I uploaded another build which had little changes, and that had DSYMs download link. This is pretty bad as am not able to symbolicate crash reports on fabric/firebase

Yeah, HFS is now loaded from a KEXT, which is cool in general but makes things hard for DTrace. It would seem logical for the HFS KEXT’s .dSYM to be included in the Kernel Debug Kit but it is not. You should definitely file a bug requesting that. Please post your bug number, just for the record. If no one else chimes in, you might try asking over on the filesystem-dev mailing list.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Seeing the same issue. We started seeing this for a build which we uploaded to Appstore connect on July 27th 2021. Ever since then all of our bitcode enabled builds uploaded to appstore connect do not have matching UUIDs between the crashes reported and the dsyms downloaded from appstore connect. Even xcode organiser is unable to symbolicate these crash logs. This issue seems to be happening for app targets and not the extension targets such as Intent Service extensions. The app extension crashes appear symbolicated on xcode organiser. If it helps our Compressed File size on appstore connect is 274MB.

But what if I don't download the archive builds from Xcode Cloud and don't have them locally? Does that mean that I won't be able to symbolicate crash? I thought the crashes would be symbolicated in the cloud. It's not the case? When you submit your app to the App Store, there's an option for you to include symbol information as part of the app for that upload. When you do so, crash reports that appear in your Xcode Organizer for that app version will be symbolicated for you already. That's a feature of the App Store, and not specific to builds created and uploaded through Xcode Cloud. However, that doesn't mean you shouldn't download the archives from Xcode Cloud, that is still a best practice. One valuable part of that is access to the dSYMs, which are incredibly detailed debugging assets. While using the dSYMs for symbolication is one function they serve, they also enable significant debugging capabilities using LLDB that aren't possible without them. The symbol information for symbolicat

Hello there, Instruments 14.0 has known issue to show disassembly for sybmols without access to DWARF information (dSym or executable with debug symbols). It was resolved in Instruments 14.1 which you can download with Xcode 14.1 from App Store or developer.apple.com/download. -- Anton

Please change to No the User script sandboxing under Build Settings. Also for further info: https://stackoverflow.com/questions/48296774/firebase-crashlytics-upload-missing-dsyms-to-see-crashes-from-1-versions-ios/79246834#79246834

This issue is definitely not resolved.We are using bitcode, symbols uploaded, and after downloading the dsyms and attempting to manually symbolicate, we are still seeing `hidden` in the stacktrace, meaning we're currently in a frightening place where we cannot fix bugs in our production app.