dsym file

.symbols files are generated when you submit machine code instead of bitcode to the App Store. They are used as part of the mechanism used to deliver symbolicated crash reports to your Xcode Organizer. They are lighter weight than the complete .dSYM file, which contains far more debugging info.

Have you been able to solve this problem ?It looks like I have similar issue.I have framework with bitcode enabled. I have BCSymbolMap and dSYMs for this framework but it looks like UUID of framework changes when it is uploaded to TestFlight and I am unable to symbilicate crash reports.I tried to add dSYM of framework as described here: https://stackoverflow.com/questions/50947279/how-to-include-dsym-file-of-an-embedded-framework-to-an-app-archive but it doesn't work - I get ITMS-90034: Missing or invalid signature when uploading to TestFlight.

Yes, I verified the UUIDs match. The problem that I got stuck on was this command: mdfind 'com_apple_xcode_dsym_uuids = *'only finds dSYM files in my Xcode archive so symbolicatecrash says that it can't find the dSYM even though it's sitting right next the .crash file.Is symbolicatecrash supposed to work for builds that haven't been archived by Xcode?I'm using Xcode 7.2 (7C68).

@DTS Engineer, Ed, there is already a thread for warning: (arm64) /Users/user/Library/Developer/Xcode/DerivedData/SomeApp-dih...wzn/Build/Products/Debug-iphonesimulator/SomeApp.app/SomeApp empty dSYM file detected, dSYM was created with an executable with no debug info. https://developer.apple.com/forums/thread/764301 In that thread you point to this thread :)

You need to check that the build UUID of the .dSYM file matches the build UUID of your app in the Binary Images section of your crash report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Easy Fix Locate the missing.framework in your Flutter app *Missing is the name of missing DSYM find ~/Library/Developer/Xcode/DerivedData -name missingframework | grep -v SourcePackages Generate the dSYM file manually xcrun dsymutil -o ~/Desktop/missing.framework.dSYM /path/to/found/missing.framework/missing Find your recent archive Go to Xcode > Window > Organizer Right-click on your most recent archive and select Show in Finder Right-click on the .xcarchive file and select Show Package Contents Navigate to dSYMs folder Copy the generated dSYM** Copy the generated Razorpay.framework.dSYM file from your Desktop Paste it into the dSYMs folder in your .xcarchive package Retry uploading or validating*

You need the original dSYM file, and as part of general practice, you should always hold on to the Xcode archives that you upload to TestFlight or the App Store, for this reason. If we rewind a few steps, what are the steps in your build process that mean that you currently have the .symbols files, but not the original dSM file? — Ed Ford,  DTS Engineer

Ok, I found the crash report. You can download it from here:Thanks.It looks to me like the null uuids reported by this command:Actually, I think that’s the other way around: that data is null because the importer has failed.The importer shouldn’t crash regardless of what the .dSYM file looks like. Please file a bug report about this, including the crash log and the .dSYM file that triggers the crash. Once you’ve done that, I’d appreciate you posting your bug number here, just for the record. You may still be able to get your original crash report symbolicated by hacking the symbolicatecrash script (preferably a copy!) to bypass Spotlight and find the .dSYM manually. It’s not something I’d done before, and my Ruby skills are woeful, but it’s probably the best way forward given this problem. Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

otool will show you linked dynamic frameworks but not static frameworks that are compiled into your main executable. You can inspect symbols in dsym files to see what is in your main app binary and look for any static frameworks, or use a service like Emerge Tools to scan for these automatically.

@DTS Engineer Sorry for the misunderstanding. I’m focusing the problem description on “Xcode 16 warning about missing symbols.” Goal: To submit my build with Xcode 16 to App Store Connect with dSYM included without getting warnings (see image ). Xcode 16: When I create an archive in Xcode 16 and submit it to App Store Connect, I receive the following warnings: “Upload Symbols Failed…” Xcode 15: When I create an archive in Xcode 15 and submit it to App Store Connect, I receive no warnings and the dSYM files are included. Xcode 16 (Using Custom Distribution & Transponder App): When I use Xcode 16 and select the distribution method as “Custom” -> “App Store Connect” > “Export”, and then upload the “app-name.ipa” via the Transponder app to App Store Connect, I receive no warnings and the dSYM files are included. I hope this clarification helps you better understand the issue. – Thomas

I recommend reading the explanation from a_periz here: https://twittercommunity.com/t/not-matching-uuid-bitcode/61000. It seems that in many situations the missing dSYM file is available in iTunes Connect, even if the Xcode Organizer Download dSYMs button says There are no dSYMs available for download.In my experience, Crashlytics showed me that a dSYM was missing, but when I went to that build's archive through the Organizer, the UUIDs of the dSYMs didn't match the UUID that was missing in Crashlytics. Typing mdfind com_apple_xcode_dsym_uuids == <UUID> into the terminal wasn't able to find the dSYM on my computer either. However, when I went to iTunes Connect > My Apps > Activity > All Builds > # > Build Details > Download dSYM, that zip file contained several dSYMs and one of them matched the UUID that Crashlytics wanted. I'm not sure if the button in the Xcode Organizer to Download dSYMs intent

Same issue here. Uploaded bitcode and included symbols, which iTunes Connect corroborates.Downloading dSYM files contains only __hidden symbols.I understand that uploading bitcode hides symbols by default, but it seems like include symbols is supposed to be the opt-in for sharing symbols with Apple?File as radar://26536862

[quote='821589022, Fat_Panda, /thread/772077?answerId=821589022#821589022, /profile/Fat_Panda'] What should I do with the .dSYM file to symbolize the crashlog.crash file? [/quote] Did you check that the build UUIDs match up? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We're also seeing the same issue here. It was still working on July 20th for our last build, but the latest build uploaded on the August 4th 2021 did not have matching UUIDs. Is this being looked at? It's quite important for us to be able to upload the matching dsym files to Firebase Crashlytics.

According to release notes of Xcode 14 Bitcode is Deprecated. https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes Since Bitcode is not enabled anymore, I think Apple is stopped producing DSYM files for builds produced by Xcode 14.