Crashlytics in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Crashlytics: What happens when a crash occurs?

In an Android app integrated with Crashlytics, what happens immediately after the app crashes?

A The app automatically restarts and sends the crash report in the background.

B The crash report is sent to Firebase immediately, even if the app is closed.

C The crash report is saved locally and sent the next time the app starts.

D The crash report is discarded unless the user manually sends it.

💡 Hint

Think about how Crashlytics handles network availability and app lifecycle.

Crashlytics saves crash reports locally when a crash happens. It sends them to Firebase the next time the app starts, ensuring reports are not lost if the app closes abruptly.

🧠 Conceptual

intermediate

Crashlytics: Purpose of custom keys

Why would you add custom keys to Crashlytics reports in your Android app?

A To add extra information about app state that helps diagnose crashes.

B To change the priority of crash reports sent to Firebase.

C To prevent certain crashes from being reported to Firebase.

D To automatically fix bugs based on the keys provided.

💡 Hint

Custom keys add context, not control over reporting or fixing.

Custom keys let you attach extra details like user actions or app state to crash reports, making it easier to understand why a crash happened.

❓ lifecycle

advanced

Crashlytics: When to initialize in Android app lifecycle?

Where is the best place to initialize Firebase Crashlytics in an Android app using Kotlin?

A Inside the Application class's onCreate() method.

B Inside the onDestroy() method of the first activity.

C Inside a background thread after user login.

D Inside the MainActivity's onStart() method.

💡 Hint

Crashlytics should be ready as early as possible in app startup.

Initializing Crashlytics in the Application class's onCreate() ensures it starts before any activity and can catch crashes anywhere in the app.

🔧 Debug

advanced

Crashlytics: Diagnosing missing crash reports

You integrated Crashlytics but notice some crashes are not appearing in Firebase console. Which of these is the most likely cause?

A Crashlytics requires manual user approval before sending reports.

B You forgot to add internet permission in AndroidManifest.xml.

C Firebase project is not linked to Google Analytics.

D The app is running in debug mode and crash reporting is disabled by default.

💡 Hint

Think about Crashlytics behavior in debug vs release builds.

By default, Crashlytics disables crash reporting in debug builds to avoid noise. You must enable it explicitly or test in release builds.

❓ navigation

expert

Crashlytics: Handling user consent before crash reporting

Your app requires user consent before sending crash reports. Which approach correctly delays Crashlytics initialization until after consent is given?

Android Kotlin

class MyApp : Application() {
  override fun onCreate() {
    super.onCreate()
    // What to do here?
  }
  fun onUserConsentGiven() {
    // Initialize Crashlytics here
  }
}

A Do not initialize Crashlytics in onCreate(); initialize it only inside onUserConsentGiven() after consent.

B Initialize Crashlytics in onCreate() but disable data collection until consent is given.

C Initialize Crashlytics in onCreate() and remove it if user denies consent.

D Initialize Crashlytics in onCreate() and send crash reports immediately regardless of consent.

💡 Hint

Crashlytics supports enabling/disabling data collection dynamically.

The recommended way is to initialize Crashlytics early but disable automatic data collection until user consents, then enable it. This avoids missing crashes and respects privacy.