[Crashlytics] Native stack not symbolicated for armeabi-v7a builds on 64-bit devices running in compatibility mode
Los mantenedores suelen responder en 1 día
@mrober ya está trabajando en esto.
Desde el 26/6/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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:
- Build an APK containing native libraries only for the
armeabi-v7aABI. - Install and run the APK on a 64-bit ARM device (e.g., Samsung SM-S911B).
- Trigger a native crash (e.g., via
SIGABRTor a deliberate null pointer dereference). - 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
-
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.
- Repeated manual uploading of symbols using the Firebase CLI (
-
The minidump is valid and can be symbolicated locally.
- A raw minidump file (from the device path
.../native/pending) from a crash on thearmeabi-v7abuild was extracted and processed locally usingminidump_stackwalkwith the corresponding symbol files. - The local symbolication was successful, producing a fully readable stack trace.
- A raw minidump file (from the device path
-
The issue is specific to
armeabi-v7aon a 64-bit host.- The same device (SM-S911B) running the
arm64-v8aversion of the same APK produces a symbolicated stack trace in the Crashlytics console without any issues.
arm-v7a stacktrace from Crashlytics
arm64-v8a stacktrace from Crashlytics
- The same device (SM-S911B) running the
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.
- Lenguaje dominante
- Java
- Estrellas
- 2.6k
- Forks
- 733
- Merge medio
- 2 d 15 h
- PR fusionados (30 d)
- 72
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firebase/firebase-android-sdk
-
api: remoteconfig
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
firebase/firebase-android-sdk#8827 ·
Los mantenedores suelen responder en 1 día
-
Crashlytics plugin writes build ID lists in directory listing order, so APKs can differ between machinesPosiblemente ocupada @mrober la tomó hace 8 días. Abiertoapi: crashlytics
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
firebase/firebase-android-sdk#8789 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
api: auth
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
firebase/firebase-android-sdk#8505 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 15/100
firebase/firebase-android-sdk#8835 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
firebase/firebase-android-sdk#8832 ·
Los mantenedores suelen responder en 1 día
Todos los issues de firebase/firebase-android-sdk
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
Los mantenedores suelen responder en 1 día
-
RIS export splits an organization name containing “and” into multiple authorsPosiblemente ocupada @Gautam-aman la tomó hoy. Abiertostatus: needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
JabRef/jabref#17821 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
FailureContext.java rounds down thresholds in lastedAtLeast()Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día