How do I symbolicate a copy/pasted crash report?

Question

I have a user who is experiencing a crash using the app store version of an iPhone app. The crash is not reported via iTunes connect and the user is unable to sync with iTu

Answer 1

One way to symbolicate a crash log is to run the following command on terminal:

xcrun atos -o MyApp.app/MyApp -arch armv7 -l 0xb7000 -f MyApp.crash

Replace the example hexadecimal number(0xb700) in the command above with the base load address. Base load address is the first memory address in the line immediately after

"Binary Images:"

To get the .app file:

1. Right click on the xcarchive file and select Show Package Contents
2. The .app file is in the Products/Applications directory.

Answer 2

This is similar to the question How to Manually Symbolicate iOS Crash to View Crash Logs

A plugin is available for Xcode under the Product menu. This plugin is available through Alcatraz package manager or can be directly downloaded from github.

This plugin internally incorporates a shell script that does the set up of running the following commands for manual crash symbolication.

1. Set an alias to symbolicatecrash.pl perl script

alias symbolicatecrash='/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks/DTDeviceKit.framework/Versions/A/Resources/symbolicatecrash'

2. To find symbolicatecrash, should it differ from the alias above:

find /Applications/Xcode.app -name symbolicatecrash -type f

3. Set the DEVELOPER_DIR variable:

export DEVELOPER_DIR='/Applications/Xcode.app/Contents/Developer'

4. With the dSYM the crash can be symbolicates as:

symbolicatecrash /path/to/MyApp_2012-10-01_Device.crash /path/to/MyApp.app.dSYM.

Answer 3

You have to have the exact dSYM that was generated along the build that is installed on the device and generated the crash report.

Some background information and steps to go through to identify the reason why symbolication won't work can be found here: http://support.hockeyapp.net/kb/how-tos-faq/how-to-solve-symbolication-problems

In addition, you might want to be more specific when saying:

When I import this manually created .crash report into XCode's Organizer, I am not able to symbolicate it.

How does the crash report look like after symbolication? Please post the full report.

Using the same Xcode that generated the app store binary is irrelevant, as said above you need the dSYM that has been generated alongside the app binary. And that dSYM has be accessible via spotlight, as the above linked article explains.

The steps explained in Symbolicating iPhone App Crash Reports do not always work. See this post for more details on that: https://stackoverflow.com/a/14810920/474794

Update: The report will not be symbolicated, because the stack frames of the threads are not formatted correctly! The lines with the 2 hex addresses, the + sign and the number in the end have to be at the end of the line above. So go into each of those lines hit the backspace/delete key to move it up and save. (don't delete the tab after the library/binary name!) Then symbolication should work. Or use this edited one: http://pastebin.com/L9r6PTXr