Breakpad symbol generation failed (exit=1) in 3.0.2

[HandyP94]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: n/a
• Firebase Component: Crashlytics Gradle Plugin
• Component version: 3.0.2
• Build on Bitrise, Build stack: Ubuntu 20.04 for Android and Docker

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

The error in #4280 still happens for me in 3.0.2. This is the stacktrace:

java.io.IOException: Breakpad symbol generation failed (exit=1), see STDERR
    at com.google.firebase.crashlytics.buildtools.ndk.internal.breakpad.BreakpadSymbolGenerator.generateSymbols(BreakpadSymbolGenerator.java:129)
    at com.google.firebase.crashlytics.buildtools.Buildtools.generateNativeSymbolFiles(Buildtools.java:306)
    at com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsBuildtools.generateNativeSymbolFiles(CrashlyticsBuildtools.kt:82)
    at com.google.firebase.crashlytics.buildtools.gradle.tasks.GenerateSymbolFileTask.generateSymbolFiles(GenerateSymbolFileTask.kt:75)

I'm on the Android Gradle Plugin version 8.1.4 and Gradle version 8.2.

The builds work on my local machine (Apple Silicon MacBook)

[lehcar09]

Hi @HandyP94, thank you for reporting the issue. Can you share the STDERR output? The binary should have been downloaded into app's build directory:

(APP-DIR) /build/crashlytics/ (VARIANT) /dump_syms/dump_syms.bin (PATH-TO-NATIVE-LIB)

To add, this issue looks similar similar to #6139. Both customers are using Ubuntu machines. Could you check if the resolution they share will work for you?

1. Update to Ubuntu LTS version 24.04
2. If you’re using Groovy DSL, could you try migrating to Kotlin DSL and see if the issue persists?

[google-oss-bot]

Hey @HandyP94. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[HandyP94]

Hey, I'm actively working on this, and will probably be able to give feedback to at least one of those solutions next week.

[HandyP94]

Although it doens't really make sense to me, changing to Kotlin DSL along with a bump in the gradle plugin version solved it for me

[tomaszrybakiewicz]

I encountered the same problem on CI after updating to the latest AGP (8.6.1), Google Services (4.4.2), and Crashlytics (3.0.2). Updating the docker image to Ubuntu 24.04 and the Gradle wrapper to 8.10.2 fixed the problem.

[contrudar]

@tomaszrybakiewicz thank you very much, updating Ubuntu thats what helped me. But how did you find it out?