---
title: Mobile: Group crashes tab
source: https://docs.newrelic.com/docs/errors-inbox/mobile-tab
---

Frequent mobile app crashes degrade the user experience and cause delays in the development lifecycle. The **Group crashes** page is designed to help your development team deliver a more stable and reliable mobile app experience to your users.

With the **Group crashes** page you can:

-   **Assess overall crash trends**: Review the **Crash rate percentage** and **Crash-free users **percentage charts to quickly identify any anomalies or patterns in crash occurrences.
-   **Filter for deeper analysis**: Utilize groups and filters to focus on specific crash attributes, such as device type, location, or custom data points.
-   **Identify patterns**: Examine the **Crash location** table for trends related to location, exception type, date, frequency, app version, and the number of affected users or devices.
-   **Monitor device impact**: Track how many unique devices are affected by crashes through the **Devices impacted** metric, which is automatically collected for mobile applications.
-   **Investigate individual crashes**: Select a crash report to view its interaction trail, event trail, thread details, attributes, and other relevant information. You can also resymbolicate or export the details to Xcode for debugging.
-   **Update crash status**: Mark the crash as `Resolved` or choose from other status options, such as `Resolved in specific version`.

![A screenshot depicting the group crashes tab in the New Relic UI](https://docs.newrelic.com/images/errors-inbox_screenshot-crop_group-crashes-tab-.webp "group crashes tab")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > Crashes (errors inbox)**: With our **Group crashes** tab you can analyze crash rate and crash free users at a glance or dive deeper into specific crash locations.

## Device impact tracking [#device-impact]

For mobile applications, New Relic automatically tracks **Devices impacted** as a key metric in the Errors inbox. This metric shows the number of unique mobile devices affected by crashes and helps you understand the scope of issues across your user base.

**Key benefits of device impact tracking:**

-   **Automatic collection**: No additional configuration required - the metric is collected automatically for all mobile entities
-   **Fallback metric**: When user impact data isn't available, New Relic displays devices impacted to ensure visibility into error scope
-   **Prioritization**: Helps you prioritize crash fixes by showing which errors affect the most devices
-   **Alerting**: You can create alerts based on devices impacted thresholds

You can query devices impacted using NRQL:

```sql
SELECT uniqueCount(newrelic.error.group.deviceImpact) 
FROM Metric 
WHERE metricName='newrelic.error.group.deviceImpact'
```

For more details on impact metrics and alerting, see [Error scope: Users, sessions, and devices impacted](https://docs.newrelic.com/docs/errors-inbox/error-scope-users-sessions-devices-impacted/).

## Suggested workflow [#workflow]

These steps outline our recommended approach to crash investigation, enabling you to gain a complete understanding of the alert event, identify contributing factors, and implement effective debugging strategies.

**Crash percentages charts: See patterns immediately**

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 [period](#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 period.)

**Groups and filters: Slice and dice the crash data**

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](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/manage-your-dashboard/#dash-time-picker) to adjust the currently selected 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.

**Queries and image links: Query crash data and share charts with others**

Mobile monitoring's **Crash analysis** charts use [default attributes for mobile events](https://docs.newrelic.com/docs/data-apis/understand-data/event-data/events-reported-mobile-monitoring), 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](https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language), and copy it to a new or existing dashboard.
-   **View query** link: View the [NRQL query](https://docs.newrelic.com/docs/nrql/get-started/introduction-nrql-new-relics-query-language) 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.

**Crash profiles: Quickly see key differences between crashed and crash-free accounts**

Crash profiles provide quick, clear insight into your mobile crash data by surfacing 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.

![mobile-crash-profiles.png](https://docs.newrelic.com/images/mobile_screenshot-full_crash-profiles.webp "Mobile crash profiles")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > (select an app) > Errors > Crash analysis > Crash profiles**: Compare crashed and crash-free sessions.

**Crash event trail: See all the events leading up to a crash**

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 by custom events you've created. For more information, see [Crash event trail](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail).

**Examine crash report details: Export to Xcode or resymbolicate your source code**

From the **Crash types** table, you can drill down into a specific [crash type](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/investigate-mobile-app-crash-report). 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.

    ![New Relic Mobile Crash Analytics: Stack trace](https://docs.newrelic.com/images/mobile_screenshot-full_stack-trace.webp "New Relic mobile crash analytics: Stack trace")

    **[one.newrelic.com > All capabilities](https://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**.

## Crashes details view [#details-view]

The **Crash summary panel** includes:

-   **Occurrences chart**: Visualizes the frequency of this specific crash over the selected period since its initial detection. If multiple occurrences are recorded, you can navigate through each instance.
-   **Crash type breakdown** : Displays the distribution of this crash across different operating system versions or affected devices.

Resolved crashes are indicated by a banner that shows the user who resolved the crash and the resolution timestamp. Note that mobile monitoring's [data retention policies apply](https://docs.newrelic.com/docs/accounts/original-accounts-billing/product-based-pricing/overview-data-retention-components/#mobile), allowing you to filter by resolved crashes for historical analysis when needed.

![A screenshot showing the crash details view in the errors inbox UI](https://docs.newrelic.com/images/errors-inbox_screenshot-full_crash-details-view.webp "crash details view")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > Crashes (errors inbox)**: Select a crash location to open the **Crash details** page.

## Triage your crashes [#triage-crashes]

The triage section associates the specific error occurrence you're viewing with its [system-created error group](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/#groups). These system-created error groups are identified by a unique fingerprint. It is this unique fingerprint that allows you to triage error groups by status updates or assignments.

For more info on how error groups are created, see [How error groups work](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/#how-groups-work), and to learn more about status and assignments, see [Error tracking](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/#assign).

![A screenshot showcasing how to triage crashes in errors inbox](https://docs.newrelic.com/images/errors-inbox_screenshot-crop_triage-crashes-with-errors-inbox.webp "triage crashes")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > Crashes (errors inbox) > Select a crash location **:  From the **Crash details** page you can triage specific error occurrences by adding status updates or assignments.

## Crash attributes [#crash-attributes]

Each crash sample provides detailed information about the device environment where the crash occurred, including:

-   **App version**: The specific version of the application in which the crash occurred.
-   **Device type**: The model of the device on which the crash occurred.
-   **OS version**: The operating system version running on the device.
-   **RAM used**: The amount of memory the application was utilizing at the time of the crash.
-   **Disk free**: The amount of available storage space on the device when the crash happened.
-   **Attributes**: Detailed attributes associated with the crash report, offering deeper insights into the context of the crash.

You can export crash details to Xcode or resymbolicate your source code, if applicable, to streamline the troubleshooting process.

## Event trail [#event-trail]

The event trail provides a chronological log of all mobile [events](https://docs.newrelic.com/docs/data-apis/custom-data/custom-events/report-mobile-monitoring-custom-events-attributes/#event-definition) leading up to a crash, aiding root cause analysis. These can be events New Relic monitors by default, or custom events. The event trail is sorted chronologically, beginning with the oldest event, which is typically the app launch, but you can modify the following:

-   **Sort**: Toggle between ascending and descending order.
-   **Event filtering**: Filter by event type, like `interaction`, `request`, or `request error`.
-   **Event details**: Expand individual events to inspect their attributes, like `responseTime`,or `requestUrl` for request events.

After you've sorted and filtered your events, you can dig a little deeper into the events that lead up to the crash by examining:

-   **Custom breadcrumbs**: Utilize the [Record breadcrumb SDK](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-breadcrumb/) to create custom `MobileBreadcrumb` events. This allows you to log specific application interactions that may be relevant to crash analysis.
-   **Handled exceptions**: Use the `recordHandledException` SDK methods for iOS and Android to annotate where exceptions are handled in your application. These annotations will automatically populate the crash event trail.

For detailed guidance on enhancing crash event trails with custom data, see [Record breadcrumbs](https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-breadcrumb/).

To fully leverage our crash analysis tools, make sure to:

-   Use the mobile SDK to create custom `MobileBreadcrumb` or `MobileHandledException` events.
-   Enable `MobileRequest` events for capturing network request data.

![A screenshot showing the event trail for group crashes in the UI](https://docs.newrelic.com/images/errors-inbox_screenshot-crop_event-trail.webp "group crashes event trail")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Mobile > Crashes (errors inbox) > Select a crash location **:  Dig deeper into the events that led up to a specific crash using our event trail.

## Mobile stack trace [#stack-trace]

The stack trace for each crash is displayed beneath the crash details. Each frame within the stack shows the associated library or package name, and method. For each crash, the mobile agent attempts to detect the specific stack frame containing the programming error responsible for the crash. If successfully detected, that stack frame appears red.

-   **iOS apps**: Source code method names and line numbers are visible if you have uploaded the corresponding dSYM files for each build.
-   **Android apps using ProGuard**: Package and method names will be de-obfuscated if ProGuard map uploading is enabled.
-   **Android native crash reports**: These reports will only display source filenames and relative code offsets.

You can use [email alerts](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/mobile-app-pages/mobile-monitoring-email-notifications/) to promptly respond to new crashes.

## Android-native crash reporting [#android-native-reporting]

[New Relic Android agent version 6.7.0](https://docs.newrelic.com/docs/release-notes/mobile-release-notes/android-release-notes/android-670), introduced enhancements to help track and diagnose native crashes, reporting, and analysis. These enhancements include signal violations and other faults that occur at the [native code](https://developer.android.com/ndk/guides) level during runtime.

These enhancements include:

-   **Native crash reports**: Signal violations and other crashes reported by the app during runtime, including:
    -   Signal 4: Illegal instruction
    -   Signal 6: Abnormal termination
    -   Signal 7: Bus error/bad memory access
    -   Signal 8: Floating-point exception
    -   Signal 1: Segmentation violation/invalid memory reference

-   **Native runtime exceptions**: The native agent will report any unhandled C++ exceptions thrown by the app during runtime, and report them as [handled exceptions](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/introduction-mobile-handled-exceptions/). Unhandled exceptions are usually fatal and will crash the application.

> #### ⚠️ IMPORTANT
>
> Native crash reporting is an incubating feature. Native crash monitoring is difficult at best, but the agent will make all best-attempts to detect and report these conditions. It may miss or incompletely report some conditions, and there may be latency viewing these conditions in the application dashboard.
>
> Symbolication of native symbols will not be supported in early NDK agent releases. When native symbols for an app are not present, the stack trace produced by a crash consists only of these obfuscated labels, which are not easily readable.

You can view detailed information about native crashes in New Relic Mobile's [**Crash analysis** UI](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes), or receive crash notifications by [email](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/receive-crash-notifications-email). You can also explore the crash data deeper with [New Relic Insights](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/crash-analysis-group-filter-your-crashes#insights), or [integrate with ticketing systems](https://docs.newrelic.com/docs/mobile-monitoring/mobile-monitoring-ui/crashes/file-tickets-mobile-app-crashes) for further investigation.

## Troubleshooting  [#profiles-disabled]

Keep in mind that profiles are disabled when there are no statistically significant differences between attributes values of crashed and crash-free sessions or there are no profiles available that match the applied filters.