Crash reporting in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Crash Report Upload Timing

When using Firebase Crashlytics in a mobile app, when are crash reports typically uploaded to the Firebase console?

A On the next app launch after a crash has occurred.

B Crash reports are sent continuously in real-time during app usage.

C Only when the user manually triggers a report upload in the app settings.

D Immediately when the app crashes, before the app closes.

💡 Hint

Think about when the app can safely send data after a crash.

Firebase Crashlytics saves crash data locally when the app crashes. It uploads the report the next time the app starts, ensuring the crash data is sent without interrupting the app during the crash.

❓ Architecture

intermediate

Crashlytics Integration Architecture

Which Firebase Crashlytics integration method ensures crash reports are collected with minimal impact on app startup time?

A Initializing Crashlytics synchronously in the main thread during app launch.

B Initializing Crashlytics asynchronously in a background thread after app launch.

C Manually triggering Crashlytics initialization only when a crash is detected.

D Disabling Crashlytics initialization to improve startup time.

💡 Hint

Consider how to balance crash data collection and app responsiveness.

Initializing Crashlytics asynchronously after app launch reduces startup delay while still enabling crash data collection.

❓ security

advanced

Protecting Crash Data Privacy

Which practice best protects user privacy when using Firebase Crashlytics crash reports?

A Anonymizing or avoiding sensitive user data in custom crash logs and keys.

B Including full user personal data in crash logs for easier debugging.

C Sharing crash reports publicly without restrictions for transparency.

D Disabling crash reporting to avoid any data collection.

💡 Hint

Think about privacy laws and user trust.

Best practice is to avoid sending sensitive user data in crash reports. Use anonymized or minimal data to respect privacy and comply with regulations.

❓ Configuration

advanced

Configuring Crashlytics for Non-Fatal Errors

How can you report a caught exception as a non-fatal error to Firebase Crashlytics in your app?

Choose the correct code snippet for reporting a non-fatal exception in Firebase Crashlytics (JavaScript for React Native):

Firebase

try {
  // some code that may throw
} catch (error) {
  // report error here
}

A firebase.crashlytics().sendNonFatal(error);

B firebase.crashlytics().log(error.message);

C firebase.crashlytics().reportException(error);

D firebase.crashlytics().recordError(error);

💡 Hint

Look for the official method to record caught errors.

The method recordError is used to send non-fatal exceptions to Crashlytics for later analysis.

✅ Best Practice

expert

Optimizing Crashlytics Data Usage in Production

To reduce network usage and respect user data limits, which is the best practice for controlling Firebase Crashlytics crash report uploads in a production app?

A Always upload crash reports immediately regardless of network type or user settings.

B Disable crash reporting entirely in production to save data.

C Upload crash reports only when the device is connected to Wi-Fi and the user consents.

D Upload crash reports only when the app is in debug mode.

💡 Hint

Consider user experience and data costs.

Uploading crash reports only on Wi-Fi and with user consent balances data usage and crash visibility.