Trying to symbolicate crash logs without dSym

My Swift app was rejected, and Apple reviewers sent me two crash logs but no dSym. Following these instructions ...

  1. Connect an iOS device to your Mac
  2. Choose "Devices" from the "Window" menu
  3. Under the "DEVICES" section in the left column, choose a device
  4. Click the "View Device Logs" button under the "Device Information" section on the right hand panel
  5. Drag your crash report onto the left column of the presented panel. Xcode will automatically symbolicate the crash report and display the results


... I am seeing the raw crash logs in Xcode, not symbolicated.


Could the problem be that I need a dSym? If so, do I request this from the reviewers, or is there a way for me to generate my own now?


Or is there something else I need to do to symbolicate these crash logs?


Screenshot of Xcode:

http://i.stack.imgur.com/X30tZ.jpg


Xcode 7.3.1

El Capitan

By the way, the app is running fine locally, so no way to generate a crash log myself.

Getting useful results from a crash log within a

.dSYM
is… well… tricky. You should be able to get the
.dSYM
you need from one of two places:
  • If you submitted a native binary, you can use the

    .dSYM
    from the
    .xcarchive
    that you submitted from.
  • If you submitted bitcode, you should be able to download the

    .dSYM
    from iTunes Connect.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Has symbolication ever worked in the Device Logs from Xcode?


It doesn't work now, and I'm seeing a few Forum posts on the subject.


Here's what I'm getting - un-symbolicated:

Filtered syslog:
None found


Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libswiftCore.dylib             0x0084eff4 0x654000 + 2076660
1   libswiftCore.dylib             0x006abcdc 0x654000 + 359644
2   raceQs WatchKit Extension     0x001e9bbc 0x1c4000 + 154556
3   raceQs WatchKit Extension     0x001e525c 0x1c4000 + 135772
4   raceQs WatchKit Extension     0x001ddc94 0x1c4000 + 105620
5   raceQs WatchKit Extension     0x001ddf0c 0x1c4000 + 106252
6   CoreLocation                   0x21551da0 0x21537000 + 109984
7   CoreLocation                   0x2155169a 0x21537000 + 108186
8   CoreLocation                   0x2153d658 0x21537000 + 26200



I have raised a bug report but don't expect a quick response.

Trying to symbolicate crash logs without dSym
 
 
Q