cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

What should I do when crash reports are not symbolicated after uploading the dSYM file?

Symptoms

First, follow the instructions here: How do I symbolicate mobile crash reports?

 

The dSYM file has been uploaded and the upload has been verified, but the corresponding crash reports do not get symbolicated.

 

Diagnosis

If the dSYM file is incomplete or does not have the necessary debug information, the EUM Server will not be able to symbolicate the crash reports.

 

Use the "dwarfdump" command to verify that the dSYM file contains debugging information. 

 

Example of output:

 

$ dwarfdump  86D24-73RC-2B32-ZY70-ABCXYZ.dSYM

----------------------------------------------------------------------

 File: 86D24-73RC-2B32-ZY70-ABCXYZ.dSYM (arm64)

----------------------------------------------------------------------

.debug_info contents:

< EMPTY >

 

Solution

Check that the dSYM file is complete and contains the necessary debugging information prior to upload.

Version history
Last update:
‎09-05-2018 04:40 PM
Updated by:
Labels (1)
Tags (2)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
0 Kudos