The App needs to be built without stripping debug symbols: then, when it crashes on a device, go into the organizer window, under the “Device Logs” section, and you should see a nice symbolicated crash log: To import the crash logs into Xcode (from, say, an email), just drag it into the organizer window like … Read more
When you get your crash report as a .txt file just follow these steps : Change the file extension .txt to .crash (eg mycrash.txt to mycrash.crash). Create a new folder in desktop and copy the mycrash.crash file to the newly created folder. Copy the .dSYM file: update: download all DSYMs from appstoreconnect activity- they are … Read more
To properly get symbols from your archived app’s dSYM file and get useful information from your BugSense crash reports (or any other crash reports for that matter): Copy the stack trace from BugSense into TextEdit or any other text editor. Make sure to use the “clipboard” icon, rather than simply copying the text. Otherwise you … Read more
EDIT :: XCode 4.3 You will want to follow the same steps as outlined in the original answer (below) with a few exceptions. First, you need to fix the Xcode path. Open a terminal and run: /usr/bin/xcode-select -print-path If it displays “/Developer” or anything but “/Applications/Xcode.app/Contents/Developer/” then it is wrong. To fix this run the … Read more
A simpler alternative: you can use the atos -l flag to make it do the maths for you. Say you’ve got the following line in your crash log that you want to symbolicate: 5 MyApp 0x0044e89a 0x29000 + 4348058 The first hex number is the stack address, and the second hex number is the load … Read more