Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to search a crash in Firebase Crashlytics?

I've migrated the application from "Fabric Crashlytics" to "Firebase Crashlytics" and successfully tested if the new crashes arrive.

But unfortunately, I don't see an option to search for an issue. I see an option to "Search by user" but if I want to search by the crash message I can't.

This is how I throw an exception:

throw new RuntimeException("FirebaseTestDebug crash");

I want to be able to search for this exception by the following string: "FirebaseTestDebug"

I can definitely do that in "Fabric Crashlytics" using the following UI: enter image description here

like image 669
Danylo Volokh Avatar asked Dec 11 '18 16:12

Danylo Volokh


People also ask

How do I find out crashes in Firebase Crashlytics?

Open your app from the home screen of your test device or simulator. In your app, press the "Test Crash" button that you added using the code above. After your app crashes, run it again from Xcode so that your app can send the crash report to Firebase.

What happened to Crashlytics?

In January 2017, Crashlytics and Fabric were acquired by Google. In September 2018, Google announces that Fabric will be deprecated and developers should use Crashlytics via Firebase.

What does Firebase Crashlytics do?

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.


1 Answers

There is no search by an Exception message in Firebase Crashlytics as of December 16, 2021.

However, you still can find exceptions like that if you know the method name from which the exception was thrown.

Please, note that the search works on:

  1. Title
  2. Subtitle
  3. Keys

While the title will be too general "RuntimeException", the subtitle will contain the name of the method where that exception was thrown. And this is what you can use to find crashes for the given message.

For example, I want to find an Exception containing the message "Can't extract confirmation code from referrer url" and I have the next piece of code:

override fun onInstallReferrerSetupFinished(responseCode: Int) {
    if (something) {
        throw RuntimeException("Can't extract confirmation code from referrer url: $referrer")
    }
}

While I can't find the lines using the internal message, I can find it using the method name: onInstallReferrerSetupFinished

Example of search

like image 125
Gaket Avatar answered Oct 21 '22 08:10

Gaket