Xcode 7 Symbolicate iOS Crash Report

crash_thumbIf Xcode cannot symbolicate the crash report automatically, you can use “Symbolicatecrash” tool to symbolicate the report manually. There are three files you’re going to need for this to succeed. The .app file (or if you have an ipa file just rename it to zip and uncompress, you’ll find the app file in that package), the .dSYM file and the .crash report.

You may want to verify that the dSYM contains symbols for that build, i.e. the .dSYM version is compatible with the .app version and that the crash report originated from that build.

First you check the .app file UUIDs (you’ll get UUID for each architecture)

Then check the dSYM UUIDs.

The UUIDs for the .app and .dSYM files should match.

Now to check if the crash report originated from the same build you can open the crash report and look for the Binary Images list and take a look at the first item in the list, inside of <UUID>. This UUID should match the above. See that UUID for arm64 architecture on the first line of the binary images in crash report <09cd023630033f30ba92738491e314b2> matches the UUID of the .dSYM and .app files 09CD0236-3003-3F30-BA92-738491E314B2.

Binary Images:
0x1000ad000 – 0x10100afff MyApp arm64 <09cd023630033f30ba92738491e314b2> /var/containers/Bundle/Application/70A13CBA-AAAD-4D6A-1FD6-499B73545CD1/MyApp.app/MyApp

In Xcode 7.3, the symbolicatecrash tool is located under:

To symbolicate a crash file you first need to export the DEVELOPER_DIR environment variable with the path to your Xcode installation, otherwise you’ll get this error:

To export the DEVELOPER_DIR environment variable use:

Now you can use the symbolicatecrash tool to symbolicate the crash report:

If you liked this blog post I’d appreciate if you followed me on Twitter

Related Post

Remember to share...Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInEmail this to someone

Leave a Reply

Your email address will not be published. Required fields are marked *