Crashlytics setup in Firebase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Firebase Crashlytics in your app.

Firebase

FirebaseCrashlytics [1] = FirebaseCrashlytics.getInstance();

Drag options to blanks, or click blank then click option'

Ainitialize

Bcrashlytics

Csetup

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names instead of variable names.

Trying to call initialization methods that don't exist.

You create an instance of FirebaseCrashlytics by calling getInstance() and assigning it to a variable, commonly named crashlytics.

2fill in blank

medium

Complete the code to enable Crashlytics collection in your app.

Firebase

crashlytics.[1](true);

Drag options to blanks, or click blank then click option'

AsetCrashlyticsCollectionEnabled

BenableCrashlytics

CstartCollection

DactivateCollection

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names that do not exist.

Forgetting to pass true as argument.

The method setCrashlyticsCollectionEnabled(true) enables Crashlytics data collection.

3fill in blank

hard

Fix the error in the code to log a custom key in Crashlytics.

Firebase

crashlytics.[1]("user_id", "12345");

Drag options to blanks, or click blank then click option'

Alog

BaddLog

CrecordException

DsetCustomKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using log which only logs messages, not key-value pairs.

Using non-existent methods like addLog.

The correct method to log a custom key-value pair is setCustomKey.

4fill in blank

hard

Fill both blanks to log a non-fatal exception with a message.

Firebase

Exception e = new Exception("Crash test");
crashlytics.[1](e);
crashlytics.[2]("Test message");

Drag options to blanks, or click blank then click option'

ArecordException

Blog

CsetCustomKey

DsendException

Attempts:

3 left

💡 Hint

Common Mistakes

Using sendException which is not a valid method.

Mixing up the order of methods.

Use recordException to log exceptions and log to add messages.

5fill in blank

hard

Fill all three blanks to disable Crashlytics collection, then enable it again, and finally log a message.

Firebase

crashlytics.[1](false);
crashlytics.[2](true);
crashlytics.[3]("Crashlytics re-enabled");

Drag options to blanks, or click blank then click option'

AsetCrashlyticsCollectionEnabled

Blog

DrecordException

Attempts:

3 left

💡 Hint

Common Mistakes

Using different method names for enabling/disabling collection.

Using recordException instead of log for messages.

Use setCrashlyticsCollectionEnabled(false) to disable, then setCrashlyticsCollectionEnabled(true) to enable, and log to add a message.

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