Search results for

dsym file

75,571 results found

Post

Replies

Boosts

Views

Activity

Reply to Lots of warnings when building with Xcode 7 with 3rd party libraries
I needed auto generated dSYM functionality (for archive) and CLANG_ENABLE_MODULES.Didn't find good solution so created my own. Just ignore output from dsymutilcd /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin sudo mv dsymutil dsymutil_org sudo nano dsymutil #file content #!/bin/bash $0_org $@ 2> /dev/null sudo chmod +x dsymutil
Jun ’16
Reply to Xcode cloud build Testflight crashes desymbolication
For apps already shipped to the App Store, there is a button in Xcode for downloading the dSYMs from App Store Connect. That doesn't apply here, because you are inquiring about the artifacts you can get from Xcode Cloud, unless you've already published the build to TestFlight with Xcode Cloud. If you're just downloading the build artifacts, there's nothing you need to do to get the dSYMs into Organizer — as long as they are on disk in a Spotlight accessible location, Xcode will find them by querying Spotlight.
Oct ’21
Reply to Symbolicating Crash Reports for Mac Catalyst App
Are you able to share the exact commands you used, and the output they produced? Case sensitivity matters, as do the quotes. Also what is the file location? This depends on Spotlight, so if you're in an unusual location or on a server, then Spotlight won't have that UUIDs indexed. Another way to come at this is look in your archive for the dSYM you expect to match, and use the dwarfdump commands in that same document to print the UUID, and then match it up with what's in the binary images section of your crash report.
Apr ’22
Reply to Xcode 16 warning about missing symbols of static framework
You should look inside the Xcode archive to see what the final built app looks like. By that I mean the innards of the .xcarchive in the Organizer, rather than the contents of the .xcframework package. There, I'd first validate what you see on disk inside the app's Frameworks folder, and then I'd also do the same for the dSYM folder. Since you're expecting a static framework, there shouldn't be a binary inside the frameworks folder, but you should confirm there isn't, and then also see what's in the dSYM folder. — Ed Ford,  DTS Engineer
Aug ’24
Reply to Why does my app crash on launch?
Thanks Quinn for pointing me in the right direction. I have managed to reproduce the results you posted above by dragging my crash report into Devices & Simulators. However it still doesn't fully symbolicate. I have looked at the Organiser in Xcode to try and access the appropriate dSYMs and get the message: 'No dSYMs were found for Version 1.0 Build 1'. I would appreciate any suggestions as to how to fully symbolicate the crash report so I know where to focus my attention. Thanks, Phil
Dec ’22
Xcode framework dsyms different scenarios explanation
Hi!I have a dynamic framework that I precompiled before linking with application.I use this framework in project.How could I extract its debug symbols?In archive I could find these symbols, but they are not named as these that could help me.They are not named as UUIDS.As I understand bitcode technology, framework symbols should be shipped with application binary.Is it correct?How could I copy them into result application archive folder without any issues?Two scenarios and four possiblities:Framework embedded into binary or not embedded.However, framework could be precompiled in different project and framework binary could be linked with project ( no compilation needed ).So a grid of possiblities:Framework embedded, compiled with binary.Framework embedded, NOT compiled with binary.Framework not embedded, compiled with binary ( possible? )Framework not embedded, NOT compiled with binary.Could anybody describe steps to include debug symbols in each situation?Thanks!
0
0
553
Jun ’17
Reply to help me to find the actual reason of crash in my app
I can not symbolicate the crash logs because the UUIDs in crash logs and dSYM (extracted from my local xcarchive file) don't match. I can't figure out why the mistach happened. In the end, I deleted two builds listed in app connect webpage (I am confused about which was the one submited and rejected), and rebuild my archive, upload, and submit once more. Now I am waiting and then decide the next action when Apple's review result comes. Beside, I found no way to download my xcarchive file previously uploaded.
Jan ’24
Reply to dSYMs not generating in Release Build
That's a bit strange, normally it's the other way around, dSYM being included in release build and not in debug. Check your schemes and make sure Archive is using Release config. Then under your project's build settings select All and Levels instead of Combined. Make sure DWARF with dSYM is selected for your release builds and that Strip Debug Symbols During Copy is set to No. Is your project relatively new? Does it have an Info.plist?
Jun ’25