Mobile app crashes can result in users submitting negative reviews, which can affect your organization's reputation. Crashes can also result in users deleting your app altogether, which affects your organization's profitability. With the Crash analysis UI, you can identify and deal with one of the largest bottlenecks in the development lifecycle: the time it takes to resolve unanticipated exceptions.
Use crash analysis features
When your development team receives an emailed crash notification, they can select the email link to review detailed information about the crash in our user interface, or analyze chart data directly through a query. The individual Crash details page also includes tracking tools for your team to follow the issue from reporting to resolution.
Our Crash analysis feature helps developers to:
Slice and dice your crash and network data (using groups and filters) to analyze trends leading to the crash.
Understand a particular user's experience by using a custom attribute.
Align issues with common characteristics in networks or devices.
Examine specific problems in a crash report that may be buried in thread breakdown data, trace details, or the trail of user interactions in the crashed session.
Quickly see trends from the Crash profiles tab.
View the crash list
To view the filterable Crash list in the New Relic UI:
Look for patterns in the Crash location table information, including location, exception type, date and number of occurrences, version, and number of users affected by the crash.
Select a crash report from the table to view its interaction trail, its event trail, thread details for individual occurrences, attributes, and more. If necessary, resymbolicate or export the crash details to Xcode so you can debug your source code more easily.
When finished, mark the crash occurrences as Resolved.
Resolved crashes include a banner identifying who resolved the crash and when. Based on mobile monitoring's data retention policies, you can filter by resolved crashes when you need to track back to historical information.
Start with the Crash rate percentage and Crash-free users percentage charts to see at a glance whether there are any unexpected spikes, dips, or patterns with crashes in general. For example:
Are there any spikes near a recent version release?
Is there a time period when the percentage of users has been affected significantly by the crash? (If the Crash-free users percentage chart is empty, there were no user sessions during the selected time period.)
You can select a group, and then filter to specific data, including:
Group the crash list by type of crash, device, location, or other custom attributes.
Show open crashes, resolved crashes, or all crashes.
Use the time picker to adjust the currently selected time period.
Filter by a specific Version or by one or more attribute Filter, such as Last Interaction, App Build, or any of the longer list of standard and custom attributes).
The selected filters appear at the top of the UI page.
Use the Top 5 occurrences chart to identify what types of crashes and how many occurred during the selected time period. This chart shows the top five crash occurrences by the group and filters you select. For example, you can group by email address (if instrumented as a custom attribute), then filter down to a specific email to examine that user's experience.
To filter or group by other attributes, use the search window, or select any of the available filters. For example, filter by type of crash, device, a specific location, or any custom attributes.
To look for other historical patterns, change the selected time period.
one.newrelic.com > All capabilities > Mobile > (select an app) > Errors > Crash analysis: Here is an example of the Top 5 occurrences chart filtered by the Crash locations group. Select any groups or filters to analyze your crash data any way you want.
Mobile monitoring's Crash analysis charts use default attributes for mobile events, along with any custom attributes you have added to this event type. To view or share the data, click the ellipsis icon.
Add to dashboard link: View the chart, and copy it to a new or existing dashboard.
View query link: View the NRQL query used to calculate the chart data.
Get as image link: Select this option to get a public URL of the chart, then share it using any media.
Supplementing the charts, the Crash report table lists crash types by location, and links them to relevant crash report details. Each row helps you find answers to questions such as:
How many of this crash type or exception occurred within the selected time period?
What is the most recent exception message?
Does a specific app version have a higher (or lower) number of users affected?
When did the exception first and last occur?
one.newrelic.com > All capabilities > Mobile > (select an app) > Errors > Crash analysis: Sort on any column to analyze patterns in the Crash reports table, then select any report to review crash details.
Sometimes it may be more useful to examine crash report data from lowest to highest. For example:
Which exception has the fewest number of occurrences?
When did a particular exception start (Earliest occurrence)?
You can change the sort order or filter options to focus on just the types of exceptions that matter the most to you and your teams.
Crash profiles provide quick, clear insight into your mobile crash data by surfacing any anomalies in your mobile application’s performance. Unexpected differences between attributes and behaviors are highlighted, illuminating key differences between crashed and crash-free accounts. You can quickly pinpoint key issues through drill-downs and filters for a fast, streamlined troubleshooting experience.
one.newrelic.com > All capabilities > Mobile > (select an app) > Errors > Crash analysis > Crash profiles: Compare crashed and crash-free sessions.
The mobile monitoring crash event trail shows you the events leading up to a crash of a mobile app. These can be events monitored by default, or custom events you've created. For more information, see Crash event trail.
From the Crash types table, you can drill down into a specific crash type. From here you can:
Explore the related thread breakdown.
Select Export crash details so you can examine source code using Xcode.
Click the View crash libraries button to see what Android map files or iOS .dSYM files we have for your application.
If you don't see the files you're expecting, upload a new Android map file or iOS .dSYM files by clicking on the Upload link. Note that uploading a new file automatically de-obfuscates or symbolicate your crash occurrence.
File a ticket and resolve the crash.
one.newrelic.com > All capabilities > Mobile > (select an app) > Errors > Crash Analysis > Crash types > (select a crash): This is an example of a stack trace that includes the option to upload a new Android map file or additional iOS .dSYM files. To analyze and debug your source code using Xcode, select Export crash details.
Configure crash report email settings
To learn how to configure email settings, see Email settings.