symbolicate crashlog using .symbols files instead of dSYMs

Developer Tools & Services General
kambala OP
Created 2d
Replies 1
Boosts 0
Views 50
Participants 2

Hi,

Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know why, here's an example:

Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS).

I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols file, but they are unable to work with it.

I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?

Replies  1
Boosts  0
Views  50
Participants  2
DTS Engineer OP
Apple
1d

You need the original dSYM file, and as part of general practice, you should always hold on to the Xcode archives that you upload to TestFlight or the App Store, for this reason. If we rewind a few steps, what are the steps in your build process that mean that you currently have the .symbols files, but not the original dSM file?

— Ed Ford,  DTS Engineer

0
symbolicate crashlog using .symbols files instead of dSYMs
First post date Last post date
 
 
Q