This section lists the Build UUID for every dynamically-linked library included in the application, as well as the Build UUID for the main application. Here is an example of the Binary images section from an exported crash report. Use the Build UUID extracted from the crash details to find the missing dSYM. Look for the Build UUID in the Binary images section of the exported crash report.If the App Image Uuid is not on the selected crash report's attributes list: From the selected crash report's Crash Details page, look for the App Image Uuid on the attribute list.From the Crash list table, select any row.Then find your app and click Crashes > Crash Analysis. Go to and click Mobile in the top nav.New Relic crash reports also contain the Build UUID of the crashing application. The Build UUID is also stored within the associated dSYM and can be extracted to identify the dSYM. Find which dSYM can be used to symbolicate a crash.Īn application may have more than one Build UUID, one attributed for each CPU architecture the application is built.Identify a unique build of an application.In this situation, you can use the Build UUID identifier to: However, every build of an application will create a new dSYM, and it can be difficult managing which dSYM is attributed to which app build. You can upload dSYMs manually or directly through the New Relic UI. If the dSYM is not uploaded to New Relic, mobile crash reports cannot be symbolicated.

Uuid generator android