Crash reporting in Firebase - Mini Project: Build & Apply

Firebase Crash Reporting Setup

📖 Scenario: You are building a mobile app and want to track crashes to improve app stability. You will set up Firebase Crashlytics to report crashes automatically.

🎯 Goal: Configure Firebase Crashlytics in your app to capture and report crashes.

📋 What You'll Learn

Create a Firebase configuration dictionary with the exact project ID and app ID

Add a configuration variable to enable Crashlytics collection

Initialize Firebase Crashlytics with the configuration

Complete the setup by enabling automatic crash reporting

💡 Why This Matters

🌍 Real World

Crash reporting helps developers find and fix app errors quickly, improving user experience.

💼 Career

Setting up crash reporting is a common task for mobile developers and cloud engineers working with Firebase.

1

Create Firebase configuration dictionary

Create a dictionary called firebase_config with these exact entries: 'projectId': 'my-firebase-project' and 'appId': '1:1234567890:android:abcdef123456'.

Firebase

# Create the firebase_config dictionary with projectId and appId
# Your code here

Hint

Use a Python dictionary with keys 'projectId' and 'appId' exactly as shown.

2

Add Crashlytics collection enabled flag

Add a boolean variable called crashlytics_collection_enabled and set it to True to enable crash reporting.

Firebase

firebase_config = {
    'projectId': 'my-firebase-project',
    'appId': '1:1234567890:android:abcdef123456'
}
# Add crashlytics_collection_enabled variable and set to True
# Your code here

Hint

Set the variable exactly as crashlytics_collection_enabled = True.

3

Initialize Firebase Crashlytics

Write a function called initialize_crashlytics that takes config and enabled as parameters and returns a dictionary with keys 'config' and 'collection_enabled' set to the passed values.

Firebase

firebase_config = {
    'projectId': 'my-firebase-project',
    'appId': '1:1234567890:android:abcdef123456'
}
crashlytics_collection_enabled = True
# Define initialize_crashlytics function below
# Your code here

Hint

Define a function that returns a dictionary with the given parameters.

4

Enable automatic crash reporting

Call the function initialize_crashlytics with firebase_config and crashlytics_collection_enabled and assign the result to a variable called crashlytics_setup.

Firebase

firebase_config = {
    'projectId': 'my-firebase-project',
    'appId': '1:1234567890:android:abcdef123456'
}
crashlytics_collection_enabled = True

def initialize_crashlytics(config, enabled):
    return {
        'config': config,
        'collection_enabled': enabled
    }

# Call initialize_crashlytics and assign to crashlytics_setup
# Your code here

Hint

Call the function with the two variables and assign the result to crashlytics_setup.

Practice

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

easy

A. To store user data securely

B. To manage user authentication

C. To improve app loading speed

D. To automatically collect and report app crashes

Solution

1. Step 1: Understand Crashlytics role

   Firebase Crashlytics is designed to track and report app crashes automatically.

2. Step 2: Compare with other options

   Storing user data, improving speed, and managing authentication are not Crashlytics functions.

3. Final Answer:

   To automatically collect and report app crashes -> Option D

4. Quick Check:

   Crashlytics = crash reporting [OK]

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

Common Mistakes:

• Confusing Crashlytics with user data storage
• Thinking it speeds up the app
• Mixing it with authentication services

2. Which Firebase Crashlytics method is used to log custom messages before a crash?

easy

A. crashlytics.sendReport()

B. crashlytics.recordError()

C. crashlytics.log()

D. crashlytics.startSession()

Solution

1. Step 1: Identify logging method

   The method to add custom logs before a crash is crashlytics.log().

2. Step 2: Understand other methods

   recordError() reports errors, sendReport() and startSession() are not valid Crashlytics methods.

3. Final Answer:

   crashlytics.log() -> Option C

4. Quick Check:

   Logging = crashlytics.log() [OK]

Hint: Use .log() to add messages before crash [OK]

Common Mistakes:

• Using recordError() to log messages
• Assuming sendReport() exists
• Confusing startSession() with logging

3. Given this code snippet, what will Crashlytics report?

try {
  throw new Error('Test crash');
} catch (e) {
  firebase.crashlytics().recordError(e);
}

medium

A. Crashlytics reports a non-fatal error with message 'Test crash'

B. Crashlytics logs a warning but no error

C. App crashes immediately without reporting

D. No crash reported because error is caught

Solution

1. Step 1: Analyze try-catch behavior

   The error is thrown but caught, so the app does not crash.

2. Step 2: Understand recordError effect

   recordError() sends a non-fatal error report to Crashlytics with the error message.

3. Final Answer:

   Crashlytics reports a non-fatal error with message 'Test crash' -> Option A

4. Quick Check:

   recordError() = non-fatal error report [OK]

Hint: recordError() reports caught errors as non-fatal [OK]

Common Mistakes:

• Thinking caught errors cause app crash
• Assuming no report if error is caught
• Confusing recordError() with crash trigger

4. You added firebase.crashlytics().log('User clicked button'); but no logs appear in Crashlytics dashboard. What is the likely issue?

medium

A. Logs only appear after a crash occurs

B. log() method does not exist in Crashlytics

C. Crashlytics SDK is not initialized properly

D. You must call sendReport() to send logs

Solution

1. Step 1: Check Crashlytics log behavior

   Logs sent by log() appear only when a crash happens afterward.

2. Step 2: Verify other options

   SDK initialization is required but if logs never appear, it's likely due to no crash. log() exists and sendReport() is not a Crashlytics method.

3. Final Answer:

   Logs only appear after a crash occurs -> Option A

4. Quick Check:

   Logs show after crash [OK]

Hint: Logs appear only after crash triggers [OK]

Common Mistakes:

• Assuming logs show immediately
• Thinking log() method is missing
• Trying to send logs manually

5. How can you ensure that a caught error with extra context is reported to Firebase Crashlytics as a non-fatal issue with custom keys?

hard

A. Only use crashlytics().log() with error message

B. Use crashlytics().setCustomKey() before recordError()

C. Throw the error again to trigger a crash

D. Call crashlytics().sendReport() after catching error

Solution

1. Step 1: Add context with custom keys

   Use setCustomKey() to add extra info about the error context.

2. Step 2: Report error as non-fatal

   Call recordError() to send the caught error along with custom keys to Crashlytics.

3. Final Answer:

   Use crashlytics().setCustomKey() before recordError() -> Option B

4. Quick Check:

   Custom keys + recordError() = detailed non-fatal report [OK]

Hint: Set keys before recordError() for context [OK]

Common Mistakes:

• Only logging message without keys
• Throwing error again causes crash
• Using non-existent sendReport() method