Also, if you use pre-launch reports to identify issues with your apps, crashes found during testing are listed with your app’s crashes and ANRs. However, because crashes found while generating a pre-launch report come from test devices, they don’t affect your crash statistics.
Find your data
- Open Play Console.
- Select an app.
- On the left menu, select Quality > Android vitals > Crashes and ANRs.
- Near the center of your screen, use the filters to help you find and diagnose issues. Alternatively, select a cluster to get more details about a specific crash or ANR error.
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 information, the logcat from the device, and a video of the error.
Crash data is available for the previous two months. For more information about how Android users opt in to share data, go to the Accounts Help Center.
If your app has a high number of crashes, go to the Android Developers site for recommended solutions.
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). ANR data is available in Play Console only.
You'll see all ANRs collected from Android devices whose users have opted in to automatically share usage and diagnostics data. Data is available for the previous two months. For more information about how Android users opt in to share data, go to the Accounts Help Center.
If your app has a high number of ANRs, go to the Android Developers site for recommended solutions.
Get more information on the Android vitals > Overview page in Monitor your app's technical performance with Android vitals.