Crashlytics setup in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Firebase Crashlytics?

Firebase Crashlytics is a tool that helps you find and fix app crashes quickly by collecting crash reports and showing detailed information about the problems.

beginner

Name the first step to set up Crashlytics in a Firebase project.

The first step is to add your app to the Firebase project and include the Firebase SDK in your app code.

beginner

Why do you need to add the Crashlytics SDK to your app?

Adding the Crashlytics SDK allows your app to send crash reports to Firebase so you can see and fix issues.

intermediate

What is the purpose of enabling automatic data collection in Crashlytics?

Automatic data collection lets Crashlytics gather crash data without extra code, making setup easier and ensuring you get crash reports.

intermediate

How can you test if Crashlytics is correctly set up in your app?

You can force a test crash in your app and then check the Firebase console to see if the crash report appears.

What is the first thing to do when setting up Crashlytics?

A Add your app to a Firebase project

B Write crash reports manually

C Deploy your app to users

D Create a new Google account

You must first add your app to a Firebase project to use Crashlytics.

Which SDK do you need to add to your app for Crashlytics to work?

A Firebase Authentication SDK

B Google Maps SDK

C Firebase Crashlytics SDK

D Firebase Storage SDK

The Firebase Crashlytics SDK collects crash data from your app.

What does enabling automatic data collection in Crashlytics do?

A Deletes crash reports after sending

B Prevents crash reports from being sent

C Requires manual crash report sending

D Sends crash reports automatically

Automatic data collection sends crash reports without extra code.

How can you verify Crashlytics is working after setup?

A Uninstall and reinstall the app

B Force a test crash and check Firebase console

C Send an email to Firebase support

D Restart your device

Forcing a test crash helps confirm Crashlytics is capturing crashes.

Where do you view crash reports collected by Crashlytics?

A Firebase console

B Google Play Store

C App Store Connect

D Your device settings

Crash reports appear in the Firebase console for your project.

Explain the basic steps to set up Firebase Crashlytics in a new app.

Think about what you do from Firebase setup to testing crash reports.

Describe how Crashlytics helps developers improve app quality.

Focus on the benefits of crash reporting.

Practice

1. What is the primary purpose of Firebase Crashlytics in an app?

easy

A. To automatically detect and report app crashes

B. To store user data securely

C. To manage app user authentication

D. To optimize app performance speed

Solution

1. Step 1: Understand Crashlytics function

   Crashlytics is designed to catch app crashes and send reports automatically to Firebase Console.

2. Step 2: Compare with other Firebase features

   Other options like data storage, authentication, and performance are handled by different Firebase services.

3. Final Answer:

   To automatically detect and report app crashes -> Option A

4. Quick Check:

   Crashlytics = crash reporting [OK]

Hint: Crashlytics = crash reports, not data or auth [OK]

Common Mistakes:

• Confusing Crashlytics with Firebase Authentication
• Thinking Crashlytics manages user data
• Assuming Crashlytics improves app speed

2. Which of the following is the correct step to initialize Crashlytics in an Android app's onCreate() method?

easy

A. FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true);

B. Crashlytics.initializeCrashlytics();

C. FirebaseApp.initializeApp(this);

D. Crashlytics.startCrashlyticsSession();

Solution

1. Step 1: Identify correct Crashlytics initialization

   The official way to enable Crashlytics collection is calling FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true);.

2. Step 2: Check other options

   Crashlytics.initializeCrashlytics() and Crashlytics.startCrashlyticsSession() are not valid Firebase SDK methods. FirebaseApp.initializeApp(this); initializes Firebase but not Crashlytics specifically.

3. Final Answer:

   FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true); -> Option A

4. Quick Check:

   Enable Crashlytics with setCrashlyticsCollectionEnabled(true) [OK]

Hint: Use FirebaseCrashlytics.getInstance() to enable collection [OK]

Common Mistakes:

• Using non-existent Crashlytics methods
• Confusing FirebaseApp initialization with Crashlytics setup
• Forgetting to enable crash collection explicitly

3. Given this Android code snippet, what will happen when the app runs?

FirebaseCrashlytics crashlytics = FirebaseCrashlytics.getInstance();
crashlytics.log("User clicked button");
throw new RuntimeException("Test crash");

medium

A. The app logs the message but does not crash

B. The app ignores the exception and continues running

C. The app crashes silently without logging

D. The app logs the message and crashes, sending a report to Firebase

Solution

1. Step 1: Analyze the code behavior

   The code logs a message to Crashlytics and then throws a RuntimeException, which causes the app to crash.

2. Step 2: Understand Crashlytics reporting

   Crashlytics captures the log and crash, then sends the crash report to Firebase Console for analysis.

3. Final Answer:

   The app logs the message and crashes, sending a report to Firebase -> Option D

4. Quick Check:

   Crashlytics logs + crash = report sent [OK]

Hint: Throw exception after logging to test Crashlytics [OK]

Common Mistakes:

• Thinking the app won't crash after exception
• Assuming logs are not sent with crash
• Believing the app ignores exceptions

4. You added Crashlytics to your iOS app but no crash reports appear in Firebase Console after forcing a crash. What is the most likely mistake?

medium

A. Calling Crashlytics.crash() before initializing Firebase

B. Forgetting to enable Crashlytics in Firebase Console

C. Not calling FirebaseApp.configure() in application(_:didFinishLaunchingWithOptions:)

D. Using an unsupported iOS version

Solution

1. Step 1: Check Firebase initialization

   Calling FirebaseApp.configure() is required but usually done correctly if app runs.

2. Step 2: Verify Crashlytics enablement in Console

   Crashlytics must be enabled in Firebase Console to receive reports; forgetting this is a common cause of missing reports.

3. Step 3: Consider other options

   Calling crash before initialization or unsupported iOS versions are less common and usually cause app errors.

4. Final Answer:

   Forgetting to enable Crashlytics in Firebase Console -> Option B

5. Quick Check:

   Enable Crashlytics in Console to get reports [OK]

Hint: Always enable Crashlytics in Firebase Console after setup [OK]

Common Mistakes:

• Skipping Crashlytics enablement in Firebase Console
• Initializing Firebase incorrectly
• Assuming all iOS versions are supported

5. You want to test Crashlytics setup by forcing a crash in your Android app. Which code snippet correctly triggers a test crash that will appear in Firebase Console?

hard

A. FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(false);

B. FirebaseCrashlytics.getInstance().log("Crash test");

C. throw new RuntimeException("Test Crash");

D. FirebaseCrashlytics.getInstance().recordException(new Exception("Test"));

Solution

1. Step 1: Identify code that forces a crash

   Throwing a RuntimeException immediately crashes the app, which Crashlytics detects and reports.

2. Step 2: Understand other options

   Logging or recording exceptions do not force a crash. Disabling collection prevents reporting.

3. Final Answer:

   throw new RuntimeException("Test Crash"); -> Option C

4. Quick Check:

   Throw exception to force crash for testing [OK]

Hint: Throw exception to force crash, not just log [OK]

Common Mistakes:

• Using log or recordException without crashing
• Disabling Crashlytics collection by mistake
• Expecting logs alone to trigger crash reports