firebase_crashlytics: Crashlytics does not show Flutter origin of NDK crashes on Android

[shahbazhashmi]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Crashlytics

Which platforms are affected?

Android

Description

My Flutter Android app uses a third-party SDK that provides its own symbol files. Recently, we integrated the Crashlytics plugin and made the necessary changes on the Android native side.

The integration works perfectly for Flutter crashes, and even Android native crashes are being reported correctly. For SDK-related crashes, we upload the symbol files (provided by the SDK) using the CLI. These symbol files allow us to view symbolicated crash logs for the uploaded symbols. However, the Crashlytics console does not display the Flutter origin of these crashes. So how can I get Flutter origin of such crashes ?

Additionally, I see several entries on the console like the following:

libc.so (Missing BuildId xxxxx)
libflutter.so (Missing BuildId xxxxx)

How can I symbolicate these?

For context, I have not done any advanced configurations for Crashlytics on the Android native side. I have only added the required dependencies and plugins in the Gradle files.

Reproducing the issue

1. Add firebase_crashlytics plugin in Flutter app which has a 3rd party SDK integrated.
2. Add following changes in Android native side.
3. Check crash log of the SDK crash on crashlytics console.

app build.gradle

plugins {
    id "com.android.application"
    id "kotlin-android"
    id "dev.flutter.flutter-gradle-plugin"
    id "com.google.firebase.crashlytics"
}

dependencies {
    // crashlytics dependencies based on product flavors : starts
    implementation(platform("com.google.firebase:firebase-bom:33.7.0"))
    implementation("com.google.firebase:firebase-crashlytics-ktx")
    implementation("com.google.firebase:firebase-crashlytics-ndk")
    // crashlytics dependencies based on product flavors : ends
}

settings.gradle

plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0"
    id "com.android.application" version '8.7.2' apply false
    id "org.jetbrains.kotlin.android" version "2.0.0" apply false
    id "com.google.firebase.crashlytics" version "3.0.2" apply false
}

Firebase Core version

3.8.1

Flutter Version

3.24.5

Flutter dependencies

Expand Flutter dependencies snippet

  firebase_crashlytics: ^4.2.0
  firebase_core: ^3.8.1

[russellwheatley]

Hi @shahbazhashmi - Flutter stack traces are different. They require using the debug symbols when you build your Flutter app.

So if you build your app like so:

flutter build <target> --obfuscate --split-debug-info=symbols

You can grab the obfuscated stack trace from Firebase Crashlytics console, save it in error.txt, and run:

flutter symbolize -d symbols/app.android-x64.symbols -i error.txt

You should see a readable stack trace.

[shahbazhashmi]

Hello @russellwheatley thanks for reply. I don't use obfuscation and I build app using flutter build apk --flavor $FLAVOR --release only. And why do I need to do this manually? Shouldn't Crashlytics handle this automatically?

[russellwheatley]

You have to remember that a crash occurring on the android side isn't going to register the dart code leading up to it as it is a separate process. Presuming you're using something like a method channel to communicate Flutter <--> Android; You would have to catch the exception on the native side which can be passed back to Flutter as a failed future, then you would have to use recordError() in the Flutter side for it to be reported to Crashlytics. If it is an uncaught exception on the android side, it will only show the android stack trace.

[shahbazhashmi]

@russellwheatley I don't think the crash is occurring on the native Android side since the SDK provides Flutter methods, and the crash happens when calling those methods. It's a fatal crash that kills the app, so I don’t think it can be caught using a try-catch block. However, we are already using runZonedGuarded for error handling, and we are invoking the Crashlytics method in the necessary places.