Iphone: Where the .Dsym File Is Located in Crash Report

iphone: Where the .dSYM file is located in crash report

Right Click on your archive -> Show in Finder -> Right click on file and click on Show package contents.

Here you will find your .dSYM file.

How to decode a Crash log using dSYM file in iOS?

First of all, you need three files: the dSYM file, the application file and the crash log.

Open the X Code, in the project navigator reveal the Products folder, and "Show in finder" the app file. Here you will find the dSYM file too. Copy them to a folder.

Now open the terminal, and navigate to the folder you copied previously the two files. Run: dwarfdump --uuid Application_name.app/Application_name
You should receive the application's UUID.
Run the following command: dwarfdump --uuid Application_name.app.dSYM - you will receive the UUID again, which should match the previously received UUID.

Open the crash log (X Code - Organizer - crashes), and find the line where appears the "Binary images" title. Here is another UUID in the first line, which should match again with the previously received in the terminal.

Now, you are assured the crash was logged in the build you are examining, so open again the crash log file, find the Thread 0 section, and there should be two lines with your application name and two addresses. Such as:

Application_name 0x123456
Application_name 0x987654

In the terminal you should run now: atos -arch armv7 -o address1 address2 (the address1 and address2 should be replaced with the previous two addresses, and the armv7 with your system's - it is shown at the lines, where you got the UUIDs).

Happy debugging!

EDIT: I would like to mention this post as base of mine.

What's the dSYM and how to use it? (iOS SDK)

dSYM files store the debug symbols for your app

Services like Crashlytics use it to replace the symbols in the crash logs with the appropriate methods names so it will be readable and will make sense.

The benefit of using the dSYM is that you don't need to ship your App with its symbols making it harder to reverse engineer it and also reduce your binary size

In order to use to symbolicate the crash log you need to drag the crash log into the device's device logs in the organizer of the machine that compiled the app binary (a machine that stores the dSYM)

If you have the dSYM but don't have the machine the compiled the app binary follow the instructions in this link in order to install the dSYM into the machine.

There is a mac app that helps you symbolicate a crash log in case you need to do it yourself.

For more information please see apple technical note TN2151

Xcode cannot symbolicate my crash logs even though I have correct .dSYM file

I was working with code back to see if there can be any impact of bitcode with help of a friend, found that while exporting archive to IPA, it asks me to rebuild with bitcode (which was checked) I just tried and unchecked it to create the IPA and this time my app crash logs were symbolicated, I still don't know why this happens because apple recomends to rebuild with bitcode while submitting apps.
I am looking for more answeres for why is it happening?
Will keep you posted (also a enlighten me if there are any misses.)

How to get dSYM files for firebase

I solved it by following the steps to get my dSYM file and uploaded into firebase as zip file

Window -> Organiser -> select archive (right click) -> show in finder
-> right click archive in finder -> Show Package Content -> dSYM -> (app name).app.dSYM

---

Related Topics