How to log non-fatal exceptions with Crashlytics

Question

I started using Firebase (Crashlytics) in my project to track app crashes. It works perfectly with crashes but how can I log non-fatal crashes, i.e. caught exceptions. I tried Crashlytics.logException(e) but it doesn't work. I see no reports in the dashboard. I saw answers suggesting to use FirebaseCrash.report(t) but this class doesn't exist in the latest version of Firebase. So does anyone know how it's done?

Dependencies:

implementation 'com.google.firebase:firebase-core:16.0.0'
implementation 'com.crashlytics.sdk.android:crashlytics:2.9.3'

Did you kill and restart your app after you logged the exception? — Doug Stevenson, Aug 06 '18 at 19:25
Even on the latest version of Crashlytics, `Crashlytics.logException(ex)` is the way to go. Are you testing on a debug or a release build? I've never had problems logging non-fatals with `Crashlytics.logException(ex)`. — Eric Bachhuber, Aug 06 '18 at 19:27
Thanks, everyone. It does work after all. It seems it just takes longer time until non-fatal exceptions are shown in the dashboard or like @DougStevenson said you have to kill and restart the app. — Egis, Aug 07 '18 at 07:48
+1 on needing to kill and restart the app. My test app has a foreground service, so I had to reinstall the app to get a new process before the report is uploaded. FYI you'll see this in logcat when the events are sent back up to Firebase Crashlytics: `I/CrashlyticsCore: Crashlytics report upload complete: ` — hcabrams, Mar 12 '20 at 19:53
Is firebase sync with `implementation 'com.crashlytics.sdk.android:crashlytics:2.9.3'` dependency ?? — milad salimi, May 17 '20 at 08:57

score 58 · Accepted Answer · edited Mar 12 '20 at 09:01

58

With the new Firebase Crashlytics you should use recordException(@NonNull Throwable throwable)

...
catch (e: Exception) {
    FirebaseCrashlytics.getInstance().recordException(e)
}
...

Here is firebase documentation stating that

edited Mar 12 '20 at 09:01

Nick Cardoso

20,807
14
73
124

answered Mar 12 '20 at 08:57

Akbolat SSS

1,761
15
23

I could not find this `recordException(e)` i think it has removed – milad salimi May 17 '20 at 08:57
1

Thank you for the link, a lot of the Firebase "getting started" docs omit the Crashlytics dependencies for some reason, but the "upgrade" guide that you posted is complete and accurate. – Andrew Koster Jul 29 '20 at 17:23
@miladsalimi maybe you were using `FirebaseAnalytics` instead of `FirebaseCrashlytics`. – rtsketo Oct 27 '21 at 09:07

score 13 · Answer 2 · edited Aug 17 '21 at 08:18

13

You can use

FirebaseCrashlytics.getInstance().recordException(e)

to log non fatal issues on crashlytics

edited Aug 17 '21 at 08:18

Jithin Jude

840
14
19

answered Aug 11 '18 at 17:23

Viswanath Kumar Sandu

2,230
2
17
34

2

not working for me same code i put in my app. i have daily 3K user but firebase did not show me one crash. – Mr X Feb 19 '19 at 16:28
Kindly check if it is properly initialized in Application class. Share your code, so that we can help you – Viswanath Kumar Sandu Feb 19 '19 at 20:11
5

there is no method named 'logException' in Crashlytics – JAHelia Mar 04 '19 at 10:21
how to see non fatal logs in firebase crashlytics console? – Nainal Apr 13 '19 at 10:22
See [docs](https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android#log_non-fatal_exceptions). You can also attach additional information to the crash report with `Crashlytics.log`. More [here](https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android#add_custom_log_messages). – Big McLargeHuge May 01 '19 at 19:43
@Nainal in Firebase, go to Crashlytics, then change the filter event type to non-fatals. – Big McLargeHuge May 01 '19 at 19:45
@David I have done this but nothing appears in the console. – Nainal May 02 '19 at 05:39
Doublecheck if you have selected the correct app. I was looking at the release version while there was also a logging for the debug version – Boy May 07 '19 at 12:46
@ViswanathKumarSandu I'm having the same issue. any luck? – Rash Mendis Jun 17 '19 at 12:14
Can you share a screenshot of your code and the fabric board. It'll help to debug it faster – Viswanath Kumar Sandu Jun 17 '19 at 12:21
Nov 2019 Try: `Crashlytics.getInstance().core.logException(Throwable(message))` – Ali Kazi Nov 11 '19 at 01:34
Hi with this line can we see the none fatal exception in firebase??? – milad salimi May 17 '20 at 08:55
yes. Firebase used Crashlytics now. So it'll be visible in firebase – Viswanath Kumar Sandu May 17 '20 at 18:04
There is no class called "Crashlytics". – Andrew Koster Jul 29 '20 at 16:56
@AndrewKoster use ```FirebaseCrashlytics``` instead. ```Crashlytics``` is the old's Fabric version. – xarlymg89 Nov 05 '20 at 11:00

score 3 · Answer 3 · answered Dec 20 '20 at 04:14

Make sure that you add the following codes in you Application class which you attached in your AndroidManifest.xml -

public class MyApplication extends Application {

    @Override
    public void onCreate() {
        super.onCreate();
        .
        .
        .
        FirebaseApp.initializeApp(this);
        FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true);
        .
        .
        .
    }
}

Then call the method where expected -

FirebaseCrashlytics.getInstance().recordException(myException)

`FirebaseApp.initializeApp(this)` is not required, It is handled internally by the Firebase libraries when initialised by the `ContentProvider`s. Also `setCrashlyticsCollectionEnabled` is enabled by default, afaik. — Darshan, Feb 02 '21 at 08:23

score 1 · Answer 4 · answered Sep 30 '20 at 19:43

Module build.gradle

 apply plugin: 'com.google.firebase.crashlytics'
 apply plugin: 'com.google.gms.google-services'
  android {...

 dependencies {
   implementation 'com.google.firebase:firebase-analytics-ktx:17.5.0'
   implementation 'com.google.firebase:firebase-crashlytics-ktx:17.2.1'

Project build.gradle

   dependencies {
    classpath "com.android.tools.build:gradle:4.0.1"
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.72"
    classpath 'com.google.gms:google-services:4.3.3'
    classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
}

MainActivity.kt

 class MainActivity : AppCompatActivity() {
    companion object {
         lateinit var mCrash: FirebaseCrashlytics           
         lateinit var instance: MainActivity
         private set
     }
override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
         instance = this
        FirebaseApp.initializeApp(instance)
         mCrash = FirebaseCrashlytics.getInstance()
           val exception = Exception("test Exception")
           mCrash.recordException(exception)

score 0 · Answer 5 · answered Apr 24 '23 at 06:35

0

Adding to the other answers, take care that recordException(e) method doesn't send exceptions in time to crashlytics as it's mentioned in their docs

Crashlytics batches logged exceptions together and sends them the next time the app launches.

answered Apr 24 '23 at 06:35

Mohamed AbdulRaouf

21
6

How to log non-fatal exceptions with Crashlytics

5 Answers5

Linked