View crashes and application not responding errors

Using Play Console, you can view data for crashes and application not responding (ANR) errors for your apps. Data comes from Android devices whose users have opted in to automatically share their usage and diagnostics data.

Find your data

1. Open Play Console.
2. Select an app.
3. On the left menu, select Quality > Android vitals > Crashes and ANRs.
4. Near the center of your screen, use the filters to help you find and diagnose issues. For additional details about a crash or an ANR error, select View details () next to the item.

Note: After you select a cluster, a separate section is displayed if an issue was found while testing your app to generate a pre-launch report. To help you troubleshoot, the section includes device information, detailed crash or ANR information, the Logcat from the device, and a video of the error.

Crashes

This page shows the crashes that contribute to your crash rate metrics. Crashes are grouped into clusters to help you identify when multiple crashes may share the same root cause.

To see user-perceived crash clusters, use the Issue visibility filter and select only the issues that happen in the foreground.

To improve your crash rate, fix crash clusters with the highest number of affected users first.

For guidance on diagnosing and fixing crashes, see Android Developers site.

Tip: User-perceived crash rate is a core vital. This metric is one of the most important technical metrics and affects the discoverability of your app on Google Play.

Application not responding (ANR)

If your app stops responding, users get a dialog that allows them to wait or close the app. When these dialogs appear, they're known as "application not responding" errors (or ANRs). ANRs on devices on Android 10 and below are available only in Play Console.

This page shows the ANRs that contribute to your ANR rate metrics. ANRs are grouped into clusters to help you identify when multiple ANRs may share the same root cause.

To see user-perceived ANR clusters, use the Issue visibility filter, and select only the issues that happen in the foreground.

To improve your ANR rate, fix ANR clusters with the highest number of affected users first.

For guidance on diagnosing and fixing ANRs, see Android Developers site.

Tip: User-perceived ANR rate is a core vital. This metric is one of the most important technical metrics and affects the discoverability of your app on Google Play.

SDK-related crashes and ANRs

Occasionally, SDKs can cause technical issues in apps. When this happens, it’s often difficult to debug and resolve the issue as it occurs in code you don’t control.

If a crash or ANR is marked as "possibly SDK-related" on the Android vitals overview page (Quality > Android vitals > Overview), and you believe the SDK code is causing the issue, you can share it with the SDK provider to expedite resolution. The issue report will include your app name, full stack trace, and other issue information. SDK providers can see issues you share in Google Play SDK Console.

SDK providers can also give guidance to app developers about issues involving their SDK. Look for "SDK provider notes" from the SDK provider on the Android vitals overview page (Quality > Android vitals > Overview), which can help you understand the root cause of the issue, or how it can be prevented. You will receive a Play Console Inbox message whenever a new note is added for an issue that affects your app.

Help us understand if the note was helpful or not by clicking the thumbs-up or thumbs-down icon at the bottom of the page.

Visit Google Play SDK Index to learn more about the SDKs you are using, and to make more informed SDK choices.

Related content

Get more information on the Android vitals > Overview page in Monitor your app's technical performance with Android vitals.