Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Relic Solution: Crash Analysis Tips and Tricks

mobile

#1

Welcome to Mobile Crash Analysis!

Here are a few ideas of great things you can do with our Crash Analysis functionality.

Where do most crashes occur in my app?

  1. Select the dropdown menu GROUP CRASHES BY and choose ‘Last Interaction’.
  2. A list of Interactions now appear on the left side. The first Interaction on the list is the most common last screen viewed before a crash.
  3. Note: To make the screen name more recognizable to a wider audience, consider renaming the Interactions (Android API, iOS API) that New Relic auto-instruments.
  4. Note: If there is a key screen that we are not capturing by default, you can instrument it by creating a custom interaction. (Android API, iOS API)
  5. Click this top Interaction to add this filter. It will now appear in the top bar.
  6. Click GROUP CRASHES BY and group by Crash Location File to find which files are associated with these crashes. The file most commonly associated will be at the top of the list.
  7. Which method in the file is the culprit?
    • Click the top file in the list to add it as a filter.
    • Click GROUP CRASHES BY and group by Crash Location Method.
    • Click the top method to add this as a filter.
  8. This looks like a great place to dive into the stack traces! Click the first item in the crash table (lower right) to navigate to the Crash details page for occurrences that match the filters you’ve defined.

A user or store just experienced a crash! How can I find the details?

You may need to update your app to capture a custom attribute for user id or store id. (Android API, iOS API)

If you’re already capturing a custom attribute like user id or store id:

  1. Select FILTER dropdown on the top bar.
  2. Search for the user/store id associated with a recent crash, and select it.
  3. You will see, for example, that a particular user experienced the same crash X times.
  4. If not already, change your GROUP CRASHES BY to be Crash Location.
  5. Click the top Crash Location to add this filter.
  6. Now remove the filter for the specific user/store id from the top bar.
  7. Change your GROUP CRASHES BY to be user/store id to see the longer list of users/stores affected by the same crash.
  8. Select the top crash in the crash list table to navigate to the crash details page.

Information to view on the details page:

  • Review the bar chart showing the common OS versions and Device types associated with this crash.
  • Expand the Interaction trail and review the stack trace.
  • Click through multiple occurrences to understand the different paths users took to arrive at the same crash, which can be useful information to debug your crash.
  • Review the full list of attributes (including any custom attributes).
  • Navigate with link “Back to the Crash analysis” (link on upper left).

Can I view this data in Insights?

  • Click on “View in Insights” from any of the charts on these pages to view the chart in Insights.
  • From Insights, add any additional filters, adjust the time window, or add the chart to one of your Insights dashboards.

Relic Solution: How to Symbolicate iOS Crash Locally
Add metadata to crash reports (e.g. user's ID in our database)
Relic Solutions: How to use different app tokens in Xcode post build script for Release vs Debug
Welcome to Crash Analysis!
Tech Talk: Mobile Crash Analysis
Explorers Hub Treasure Hunt