fix(crashlytics,android): fix an issue with deobfuscating flavored builds

[Lyokone]

Description

The firebase crashlytics:symbols:upload CLI uses the ELF build ID (from .note.gnu.build-id) when uploading Dart symbols, but the FlutterFire plugin was reporting the Dart VM's internal snapshot build ID (from the stack trace build_id: line) at crash time. These are two different identifiers that can diverge, especially on AAB + flavor + obfuscation builds, causing Crashlytics to fail to match uploaded symbols to crash reports.

The fix reads the ELF build ID directly from libapp.so at runtime and uses that when reporting to Crashlytics, ensuring consistency with the upload side.

Related Issues

• Fixes [crashlytics]: Flavors + AAB + obfuscate builds do not produce deobfuscated Dart stack traces #18080

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

• Yes, this is a breaking change.
• No, this is not a breaking change.

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.