View and analyze crash and application not responding reports

To see an overview of crashes and ANRs over time on the Crashes and ANRs page, do the following:

1. Open SDK Console and select SDKs on the left menu.
2. Click on the SDK that you want to view crash or ANR information for.
3. On the left menu, select Crashes and ANRs.
4. Use the filter on the top right of the page to choose the time period you want to view the data from. You can choose Last 7 days, Last 14 days, Last 28 days, or Last 56 days. The chart will filter the data displayed based on your selection.
5. You can also filter the results by SDK version, Android version, device model and number of affected apps. By default, the report is filtered to only show issues that affect 5 or more apps.
6. All newly reported issues are classified as "Open" by default. You can update an issue’s classification (for example, to "Fixed") from a specific Crash details or ANR details page or the main Crashes and ANRs page, and then filter the issues by classification on that page.
   • Note: For any classified issues, we encourage you to add an issue note. Issue notes allow you to relay important details and context around how to resolve the crash or ANR, which is displayed in Google Play Console to apps affected by the issue. To learn more about issue notes, see View issue details.

The chart shown on the Crashes and ANRs page shows the number of occurrences, the number of affected users, and the number of affected apps by day.

All reported issues are listed under "Issues" below the chart. For each issue, you can see the number of affected users and apps, the number of occurrences, and the date the issue last occurred. The list of issues is sorted by the highest to lowest number of occurrences.

To view issue details for a specific crash or ANR, do the following:

1. Open SDK Console and select SDKs on the left menu.
2. Click on the SDK that you want to view crash or ANR information for.
3. On the left menu, select Crashes and ANRs.
4. Scroll down to the "Issues" table.
5. Click the right arrow () next to the issue listing you want to view.
6. As with the Crashes and ANRs page, use the filter on the top right of the page to choose the time period you want to view data from. You can choose Last 7 days, Last 14 days, Last 28 days, or Last 56 days; the chart will filter the data displayed based on your selection.
7. If you previously added a note for this issue for developers, you can view the note by clicking Show more next to "Note for app developers." You can also click Edit note if you want to change it. Learn more about issue notes below.

The Crash details or ANR details page shows the same information as on the Crashes and ANR page, specific to a single crash or ANR cluster, including the number of affected users and apps, the number of occurrences, and the last occurrence date. Similar to the chart on the Crashes and ANRs page, the chart on the Crash details or ANR details page displays this data visually, by day.

Below the chart, you can view more granular issue information sorted by SDK version (so you can identify which versions of your SDK are impacted), Android version, and device model.

To see the full list of SDK versions, Android versions, or devices, click Show all below the charts. Below these breakdowns, you’ll find the stack trace itself. To copy the stack trace to your clipboard, click the copy symbol () next to the stack trace.

To help protect developer information, app frames are shown as <private>. Each <private> frame represents one or more adjacent frames that have been redacted because they come from the app that has crashed or is not responding, a code library your SDK does not depend on, or a library your SDK is dependent on but is unknown to the system.

There can often be several variations of the stack trace for the same issue. Use the navigation bar at the top right of the "Stack trace" section to navigate between them. This can be the result of changes in line numbers across different SDK versions or differences between devices and OS versions. If there is only one stack trace, it may be because other variations are hidden for privacy reasons.

Note: If your SDK is obfuscated you should upload your deobfuscation files in order to get deobfuscated stack traces and allow SDK Console to group identical crashes or ANRs across different SDK versions.

You can add notes to any crashes or ANRs listed on the Crashes and ANRs page in SDK Console in order to help app developers understand what caused the issue or how it can be prevented.

By clearly communicating through these notes, you can help app developers understand the nature of a crash or ANR. This includes clarifying if the issue is with the SDK, an integration problem, or an external factor. This can help you build stronger developer relations, reduce confusion, potentially decrease direct support inquiries, and empower app developers to take appropriate actions—such as updating the SDK, correcting their integration, or understanding known limitations.

We recommend you include as much information as possible, for example, the cause of the crash or ANR, how to resolve it, or how it can be prevented. You can also add links to the SDK's documentation, issue trackers, or other guidance. The message will be shown to all app developers affected by this issue so it should not address an individual developer or include salutations.

When you add a note, it's displayed in Google Play Console on the Crashes and ANRs page of each app the crash or ANR affects.

Note: Developer Notes can’t be deleted but are editable, so you'll be able to adjust the information you provide.

To add a note to a crash or an ANR, do the following:

1. Open SDK Console and select SDKs on the left menu.
2. Click on the SDK that you want to view crash or ANR information for.
3. On the left menu, select Crashes and ANRs.
4. Scroll down to the Issues table.
5. Click the right arrow () next to the issue listing if you want to add a note to.
6. On the top right of the Crash details or ANR details page, click Add note for app developers. This opens a screen in which you can choose a crash status and add or edit your note, as shown in the screenshot below.
7. Next to Crash status or ANR status, choose a category.
8. Enter your note in the text box.
   • Write a clear, concise, and actionable note (see examples below). You can use up to 500 characters.
   • Note: You can add links to the SDK’s documentation, issue trackers, or any other external destination where you provide crash-related guidance to developers.
   • Recommended: Have someone on your team review the content of the note before you proceed.
9. When you're finished, click Add note. After you add a note, it can't be deleted. You can, however, edit them by going back to the Crash details page for the crash or ANR details page for the ANR, and clicking Edit note.
10. Once submitted, the note will be in a Pending state. It may take a few days for the new note to go live and for developers to start seeing it in Play Console.

What happens after a note is updated in the SDK Console

• Once the developer note is submitted through the SDK Console interface, it enters a review queue.
• The note will be reviewed by the Play Developer Team. 
• After the review and approval by the Play Developer Team, the developer note will be published.
• Upon publication, the note becomes visible within the Google Play Console to the app developers whose applications are affected by that specific crash or ANR cluster and are using your SDK.

Developer note categories and example notes

Below are the categories and example notes to guide your communication:

App developers can share issues which involve your SDK in order to help you debug your crashes or ANRs. Shared crashes or ANRs are displayed in SDK Console (Crashes and ANRs > Developer reported issues). Reported issues include the app name, a full stack trace of the crash or ANR, and additional crash or ANR information. If the Developer reported issues is not visible, this means that app developers have not shared any crashes or ANRs yet. We recommend encouraging app developers to share the issues they experience using View crashes and application not responding errors article.

The screenshot below shows an example of a developer reported issue:

If you have guidance to share with app developers about the reported crash or ANR, you can add an issue note (see Use issue notes to help app developers).

We will notify you by email when an app developer shares a crash or ANR involving your SDK. If you're not interested in receiving emails, you can opt out (go to Inbox > Manage email preferences).