Created
April 14, 2015 12:09
-
-
Save mitchcohen/464f99c59060d68b06fe to your computer and use it in GitHub Desktop.
Symbolicating Xcode crash reports
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now and then I need to manually symbolicate an Xcode crash report. Xcode can often do this, but not always. Here are steps that are specifically for a Watch Extension, but can be easily applied to just about anything. | |
You need the Watch Extension's dSYM from the archive created when you submitted the app. The general form: | |
$ symbolicatecrash report.crash app.dSYM | |
or more specifically, for a WatchKit Extension: | |
$ export DEVELOPER_DIR=`xcode-select --print-path` | |
$ /Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash ~/Desktop/CrashLog1.crash ~/Desktop/yourApp.xcarchive/dSYMs/yourApp\ WatchKit\ Extension.appex.dSYM > ~/Desktop/CrashLog1Symbolicated.crash | |
The above symbolicates the crash file "CrashLog1.crash" (located on your Desktop) with a WatchKit Extension named "yourApp WatchKit Extension" within the application archive "yourApp" (also located on your Desktop), and puts the symbolicated crash report into CrashLog1Symbolicated.crash (Again, on your Desktop). | |
The above path for symbolicatecrash assumes Xcode 6.3. The symbolicatecrash tool has moved around between versions. If this doesn't work in some other version, use: | |
$ find /Applications/Xcode.app -name symbolicatecrash | |
to find it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment