Log Non-fatal errors on Crashlytics

android crashlytics crashlytics-android
Eselfar picture Eselfar · Mar 29, 2017 · Viewed 20.5k times · Source

On iOS it's possible to use recordError(error) to log non-fatal errors on Crashlytics but apparently this feature is not available for Android.

The only alternative I found is to use logException(e). I manage errors on my app and I want to log when specifics errors codes are returned. So, on Crashlytics I'd like the non-fatal errors to be referenced by the errorCode. But using the logException(e) method, errors are referenced by the method where logException(e) has been called.

How can I do that?

Answer

Nicolás Carrasco picture Nicolás Carrasco · May 26, 2017

What I do in order to report a non-fatal issue is to log an exception using the following code (remember you can throw any subclass of Exception):

Crashlytics.logException(new Exception("My custom error message"));

Related questions

Fabric's Crashlytics with Firebase can't be disabled for DEBUG builds

I have an app that utilises Fabric's Crashlytics via Firebase. The following is the first thing executed in my Applications onCreate CrashlyticsCore crashlyticsCore = new CrashlyticsCore.Builder() .disabled(BuildConfig.DEBUG) .build(); Fabric.with(this, new Crashlytics.Builder().core(crashlyticsCore).build()); Nonetheless, …

Read More
Firebase Crashlytics custom log does not appear in the console

I've been testing Firebase Crashlytics and even though the normal crash report works right I can't success trying to generate a custom as it says the documentation. Crashlytics.log(msg); I also would like to know wether setting the user …

Read More
Firebase Crashlytics not reporting crashes when manually enabled

Crashlytics works just fine without opt-in reporting. But it stops reporting anything as soon as I set up opt-in reporting according to the tutorial. Specifically, I added the following content to AndroidManifest.xml <meta-data android:name="firebase_crashlytics_collection_…

Read More