Join us in person and online for Firebase Summit on October 18, 2022. Learn how Firebase can help you accelerate app development, release your app with confidence, and scale with ease. Register now

Get started with Firebase Crashlytics

Stay organized with collections Save and categorize content based on your preferences.

This quickstart describes how to set up Firebase Crashlytics in your app with the Crashlytics Flutter plugin so that you can get comprehensive crash reports in the Firebase console.

Setting up Crashlytics involves using both a command-line tool and your IDE. To finish setup, you'll need to force a test exception to be thrown to send your first crash report to Firebase.

Before you begin

  1. If you haven't already, configure and initialize Firebase in your Flutter project.

  2. Recommended: To get features like crash-free users, breadcrumb logs, and velocity alerts, you need to enable Google Analytics in your Firebase project.

    All Android and Apple platforms supported by Crashlytics (except watchOS) can take advantage of these features from Google Analytics.

    Make sure that Google Analytics is enabled in your Firebase project: Go to > Project settings > Integrations tab, then follow the on-screen instructions for Google Analytics.

Step 1: Add Crashlytics to your Flutter project

  1. From the root of your Flutter project, run the following command to install the Crashlytics Flutter plugin:

    flutter pub add firebase_crashlytics
  2. From the root directory of your Flutter project, run the following command:

    flutterfire configure

    Running this command ensures that your Flutter app's Firebase configuration is up-to-date and, for Android, adds the required Crashlytics Gradle plugin to your app.

  3. Once complete, rebuild your Flutter project:

    flutter run

Step 2: Configure crash handlers

You can automatically catch all errors that are thrown within the Flutter framework by overriding FlutterError.onError with FirebaseCrashlytics.instance.recordFlutterFatalError:

void main() async {

  await Firebase.initializeApp();

  // Pass all uncaught errors from the framework to Crashlytics.
  FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalError;


If you're using zones, instrumenting the zone’s error handler will catch errors that aren't caught by the Flutter framework (for example, in a button’s onPressed handler):

void main() async {
  runZonedGuarded<Future<void>>(() async {
    await Firebase.initializeApp();

    FlutterError.onError =

  }, (error, stack) =>
    FirebaseCrashlytics.instance.recordError(error, stack, fatal: true));

For examples of how to handle other types of errors, see Customize crash reports.

Step 3: Force a test crash to finish setup

To finish setting up Crashlytics and see initial data in the Crashlytics dashboard of the Firebase console, you need to force a test exception to be thrown.

  1. Add code to your app that you can use to force a test exception to be thrown.

    If you’ve added an error handler that calls FirebaseCrashlytics.instance.recordError(error, stack, fatal: true) to the top-level Zone, you can use the following code to add a button to your app that, when pressed, throws a test exception:

        onPressed: () => throw Exception(),
        child: const Text("Throw Test Exception"),
  2. Build and run your app.

  3. Force the test exception to be thrown in order to send your app's first report:

    1. Open your app from your test device or emulator.

    2. In your app, press the test exception button that you added using the code above.

  4. Go to the Crashlytics dashboard of the Firebase console to see your test crash.

    If you've refreshed the console and you're still not seeing the test crash after five minutes, enable debug logging to see if your app is sending crash reports.

And that's it! Crashlytics is now monitoring your app for crashes and, on Android, non-fatal errors and ANRs. Visit the Crashlytics dashboard to view and investigate all your reports and statistics.

Next steps