Forcing crash symbolication in crashes organizer and Xcode 7

Question

Currently, my crash organizer looks as follows.

I have not really worked with crash logs before, but to me the crashes do not look symbolicated. I am unable to find whe

Answer 1

What you're seeing is that the SDK classes like UITableView are symbolicated, but classes from your "YLSA" app are not. Both should be symbolicated automatically, but in my experience one or the other (or both) often do not symbolicate. I've been developing for iOS for five years and this has been a persistent problem through all the different Xcode versions.

I'm seeing the same problem as you in Xcode 7, but I was able to symbolicate my logs with this workaround:

1. In the list of crash logs, right-click the desired log and select Show in Finder. This will show you a package containing one or more .crash files and some metadata.
2. Navigate through the package until you find a crash log. You will see that the same info has or hasn't been symbolicated here.
3. In Xcode, open the Devices window and select a connected device, then click the View Device Logs button.
4. Drag the crash log in step 2 from the Finder into the list of logs for this device.
5. When I do this, I never see the log I added appear in the list, but if I click the headings once or twice to re-sort the list, then I see it.
6. After a moment, the crash log will become completely symbolicated.

If you already have a lot of logs in your list, you can compare the date, iOS version and hardware model as you view the log in the Finder to the logs in Xcode to make sure you're viewing the same log. Then look at the line that says "Triggered by Thread" to get the thread number that crashed, then scroll down to that thread to see the code that triggered the crash.

This worked for me today with Xcode 7. I hope it helps you!

Answer 2

When you submit apps through Xcode, an option will appear to include debug symbols. Next time you submit an app version, be sure to select that; if you did not, that might explain the problem you're seeing. Unfortunately there's no way to retroactively do that for app versions already submitted, so you'll have to wait until you're ready to submit the next version to see if that was the problem.