---
title: Crashlytics in the Firebase Console
description: >-
  Reviewing Crashlytics reports in the Firebase console: issue grouping, logs
  and keys on a report, closing issues, and ANR collection on Android.
next: /database/usage
previous: /crashlytics/android-setup
---
> ## Documentation Index
> Fetch the complete documentation index at: https://rnfirebase.io/llms.txt
> Use this file to discover all available pages before exploring further.

## Prerequisites

- Crashlytics installed and collecting reports per [Crashlytics usage](/crashlytics/usage) (including [Android Additional Setup](/crashlytics/android-setup) when using React Native CLI Android).
- Access to the [Firebase Console](https://console.firebase.google.com/) for the same Firebase project your app uses.
- At least one forced crash or `recordError` event from a device or emulator after a full app restart (Crashlytics uploads queued reports on launch).

# Overview

Once you have Crashlytics up and running in your app, open the Crashlytics dashboard in the Firebase Console
and start reviewing the reports as they come in. If this page still tells you to set up, build or run your app
then Crashlytics is not set up correctly in your app (see [Usage](/crashlytics/usage)).

> Keep in mind when testing Crashlytics that collection is [disabled in debug builds](/crashlytics/usage#enable-debug-crash-logs) unless `crashlytics_debug_enabled` is `true`. If you are struggling to test your crash report integration, [this article about configuring and testing Crashlytics](https://invertase.io/blog/react-native-firebase-crashlytics-configuration) might help.

The report types you see map to the methods on the [usage](/crashlytics/usage) page:

- A fatal crash, for example from `crash`, or from an unhandled JavaScript exception that the module records.
- A non-fatal event from `recordError` (see [Error Reports](/crashlytics/usage#error-reports)).
- A non-fatal event from an unhandled promise rejection in a release build.

> If you are certain that your app has produced error reports, but none are visible, try restarting your app fully. Crashlytics only uploads reports upon launching the app.

## Issues

Under issues, Firebase has gathered all the reports from your app and organized them into separate issues, where each
issue is a unique crash or stack trace in your app. The `crash` method throws an uncaught `RuntimeException` with the message `Crash Test` on Android and
causes a native crash on iOS, so using it repeatedly on the same platform adds reports to the same issue.

# Managing issues

By clicking on a specific issue, you can view its statistics and all the associated reports in more detail.

Here you're shown the breakdown of this issue by date, device and operating system. At the bottom you can browse specific
reports and view their specific contents. The logs part of a report shows the messages you added with `log`. By navigating to
data you can view information about the platform where the report was generated and information about the associated user,
which is set with `setUserId`. Under keys you can see the custom attributes that you attached with `setAttribute` and `setAttributes`.

## Closing issues

In the top right there is a button that says 'Close'. After having addressed an issue you can close it, allowing
you to filter it out in the overview by selecting 'Open' under 'Issue state', when clicking on the 'Filter issues' button.
When the same issue re-occurs, it will automatically open again. By clicking the arrow next to the button you can mute the
issue, preventing this from happening.

# Android ANR Collection Support

Crashlytics can also collect Application Not Responding (ANR) issues that occur when the UI thread of an Android app is blocked for too long.
For more information on ANR see the
[android developer documentation](https://developer.android.com/topic/performance/vitals/anr).

ANR collection is a feature of the native Firebase Android Crashlytics SDK. React Native Firebase has no JavaScript API for it.
