All Collections
Advanced usage
Symbolicating an iOS crash
Symbolicating an iOS crash

Using your build's dSYM file to get the full stacktrace of your crashes

Jordi Giménez avatar
Written by Jordi Giménez
Updated over a week ago

Bugfender helps you collect your application crashes so you know about them and take action to fix them. However, the stacktraces are sometimes not easy to understand because the symbols (the names of the objects and methods) have been removed by the compiler in order to optimize the build.

Bugfender automatically symbolicates stacktraces if the symbol information is embedded in the application. Usually Debug and Release builds contain symbol information but Archived builds do not.

If symbol information is not present, the stacktrace will contain memory addresses (hex numbers like 0x010e8a3713) instead of method names. You can recover those method names with a dSYM file that is stored on the computer that did the archiving of the application.

Here are the steps to find the dSYM file:

  • Open Xcode.

  • Select Window -> Organizer

Step 1
  • Right click on Archive and select 'Show in Finder'

Step 3
  • Select 'Show Package Content' for archive

Step 4
  • Project.xcarchive contains dSYMs, Info.plist and Products

Step 5
  • dSYMs folder contains dSYM file of your project. Upload this file to Bugfender.


These are the reasons why most often symbolication doesn't work:

  • The dSYMs must match the application version. If you upload symbols from a different version, they will not work. Please note each time a project is archived the symbols files are different, even if the code didn't change.

  • The dSYMs directory containing all the symbols files needs to be zipped and uploaded as a single file.

  • If you're using Bitcode, the dSYM files on your computer will not work. You need to download them from App Store Connect, because the application is compiled again there and the dSYM files are different.

Did this answer your question?