[Crashlytics] Native stack not symbolicated for armeabi-v7a builds on 64-bit devices running in compatibility mode

未关闭
  • 哪里不对？
#8,325 3 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@mrober 已经在做这个了。

开始于 2026年6月26日。

评估

这个 Issue 还没有评估数据。

描述

api: crashlytics
Describe your environment
  • Firebase Component: Crashlytics
  • SDK Version: com.google.firebase:firebase-crashlytics-ndk:19.2.1
  • Gradle Plugin Version: com.google.firebase:firebase-crashlytics-gradle:2.9.9
  • Firebase CLI Version (for manual upload): 15.21.0
  • Android Gradle Plugin (AGP): 8.10.1
  • NDK Version: 29.0.14206865
  • Device: Samsung SM-S911B (Android 16)
Describe the problem

Native crash stacks are not symbolicated in the Firebase Crashlytics console for armeabi-v7a (32-bit) builds when running on a 64-bit device in compatibility mode. The same build works correctly on a native 64-bit (arm64-v8a) APK on the same device.

Steps to reproduce:
  1. Build an APK containing native libraries only for the armeabi-v7a ABI.
  2. Install and run the APK on a 64-bit ARM device (e.g., Samsung SM-S911B).
  3. Trigger a native crash (e.g., via SIGABRT or a deliberate null pointer dereference).
  4. Observe the crash report in the Firebase Crashlytics console.

Expected result:
The crash report is successfully received, and the native stack trace is fully symbolicated (showing function names and line numbers).

Actual result:
The crash report is successfully received, but the native stack trace is not symbolicated. Only memory addresses or raw function offsets are shown.

Additional investigation and findings

  1. The symbols themselves are delivered.

    • Repeated manual uploading of symbols using the Firebase CLI (firebase crashlytics:symbols:upload) did not resolve the issue, ruling out a CI/upload problem.

  2. The minidump is valid and can be symbolicated locally.

    • A raw minidump file (from the device path .../native/pending) from a crash on the armeabi-v7a build was extracted and processed locally using minidump_stackwalk with the corresponding symbol files.
    • The local symbolication was successful, producing a fully readable stack trace.

  3. The issue is specific to armeabi-v7a on a 64-bit host.

Key Question

The local symbolication test confirms that the minidump and symbols are valid. The problem therefore appears to be specific to the backend processing of minidumps generated from a 32-bit (armeabi-v7a) process running on a 64-bit device. Is this a known limitation or bug?

Suggested hypothesis

The local symbolication test confirms that the minidump and symbols are valid. The problem therefore appears to be specific to the backend processing of minidumps generated from a 32-bit (armeabi-v7a) process running on a 64-bit device.

While the issue is unlikely to be related to 16KB page alignment (as this is not a strict requirement for armeabi-v7a), it may be caused by differences in how the 32-bit unwind data is interpreted by the backend, or a bug in the backend's minidump processing for this specific scenario.

P.S

We are considering updating the Firebase Gradle plugin to 3.x.x and the Firebase BoM to 34.x.x, but would appreciate guidance before doing so.

主要语言
Java
星标
2.6k
派生
733
平均合并
2 天 15 小时
30 天内合并 PR
72

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

firebase/firebase-android-sdk 的其他 Issue

查看 firebase/firebase-android-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。