当我使用Fabric Crashlytics时出现了问题,而现在使用Firebase Crashlytics最新版本时,该问题仍然存在。一切都基于official NDK docs实现,并且符号(cSYM)文件在每次构建后都会正确上传。我设法产生了一个有意的崩溃以比较逻辑删除并报告了本机崩溃回溯,结果如下:
在Firebase控制台上报告的崩溃:
崩溃保存的逻辑删除文件:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/klteduosxx/klte:5.0/LRX21T/G900FDXXU1BOJ1:user/release-keys'
Revision: '14'
ABI: 'arm'
pid: 652, tid: 1160, name: AsyncTask #5 >>> com.mnhaami.pasaj <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'stack corruption detected'
r0 00000000 r1 00000488 r2 00000006 r3 00000000
r4 656f3db8 r5 00000006 r6 00000016 r7 0000010c
r8 656f3878 r9 00000000 sl 134eaf00 fp 13f14800
ip 00000488 sp 656f37f8 lr b6eeefd5 pc b6f11b74 cpsr 600d0010
d0 ffffffffffffffff d1 ffffffffffffffff
d2 ff816306ff836406 d3 ff795f04ff7e6206
d4 ffff000000000000 d5 0000000000000003
d6 ffff000000000000 d7 ffffffffffffffff
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0000000000000000 d17 6e6f697470757272
d18 ff916d0aff997208 d19 ff825f0aff896708
d20 ff715613ff785a11 d21 ff6b520fff6b520f
d22 ff6f5309ff6e530e d23 ff775b07ff735609
d24 0000000000000000 d25 0000000000000000
d26 0002000100010001 d27 0002000200020002
d28 0080008000800080 d29 0080008000800080
d30 0800080008000800 d31 0800080008000800
scr 2800001b
backtrace:
#00 pc 00036b74 /system/lib/libc.so (tgkill+12)
#01 pc 00013fd1 /system/lib/libc.so (pthread_kill+52)
#02 pc 00014bef /system/lib/libc.so (raise+10)
#03 pc 00011531 /system/lib/libc.so (__libc_android_abort+36)
#04 pc 0000fcbc /system/lib/libc.so (abort+4)
#05 pc 00012701 /system/lib/libc.so (__libc_fatal+16)
#06 pc 000368fb /system/lib/libc.so (__stack_chk_fail+6)
stack:
656f37b8 00000001
656f37bc 00430000
656f37c0 00550000
656f37c4 00000000
656f37c8 00430000
656f37cc b4e18218
656f37d0 00000000
656f37d4 2f94ff4a /dev/ashmem/dalvik-main space (deleted)
656f37d8 9866fb50
656f37dc 2f94ff4a /dev/ashmem/dalvik-main space (deleted)
656f37e0 656f3db8 [stack:1160]
656f37e4 00000006
656f37e8 00000016
656f37ec 00000488
656f37f0 00000000
656f37f4 b6eeefcd /system/lib/libc.so (pthread_kill+48)
#00 656f37f8 656f3db0 [stack:1160]
........ ........
#01 656f37f8 656f3db0 [stack:1160]
656f37fc 00000006
656f3800 00000000
656f3804 656f3820 [stack:1160]
656f3808 656f3898 [stack:1160]
656f380c b6eefbf3 /system/lib/libc.so (raise+14)
#02 656f3810 656f381c [stack:1160]
656f3814 b6eec535 /system/lib/libc.so (__libc_android_abort+40)
#03 656f3818 000000a8
656f381c ffffffdf
656f3820 00000000
656f3824 8c93ac00
656f3828 ae907e40
656f382c 2f94ff4a /dev/ashmem/dalvik-main space (deleted)
656f3830 93bcd2fc
656f3834 b4bc0435 /system/lib/libart.so (art::CheckJNI::GetIntArrayRegion(_JNIEnv*, _jintArray*, int, int, int*))
656f3838 b6f44e04
656f383c b6eeacc0 /system/lib/libc.so (__bionic_clone)
#04 656f3840 00000000
656f3844 b6eed705 /system/lib/libc.so (__fortify_chk_fail)
#05 656f3848 b6f359a5 /system/lib/libc.so
656f384c 656f385c [stack:1160]
656f3850 8f38e000
656f3854 b6f118ff /system/lib/libc.so (__stack_chk_fail+10)
656f3858 b6f359a5 /system/lib/libc.so
656f385c 2f94ff4a /dev/ashmem/dalvik-main space (deleted)
656f3860 8f38e000
656f3864 00000000
我的gradle配置如下:
项目build.gradle:
buildscript {
repositories {
google()
jcenter()
mavenCentral()
maven { url "https://jitpack.io" }
}
dependencies {
classpath "com.android.tools.build:gradle:3.6.3"
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.61"
classpath "com.google.gms:google-services:4.3.3" // Google Services plugin
classpath "com.google.firebase:perf-plugin:1.3.1" // Performance Monitoring plugin
classpath "com.google.firebase:firebase-crashlytics-gradle:2.1.1"
}
}
allprojects {
repositories {
google()
jcenter()
mavenCentral()
maven {
url 'https://jitpack.io'
}
flatDir {
dirs 'libs'
}
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
应用模块build.gradle:
repositories {
maven { url 'http://dl.bintray.com/piasy/maven' }
mavenCentral()
}
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: 'com.google.firebase.firebase-perf'
android {
externalNativeBuild {
ndkBuild {
path 'src/main/jni/Android.mk'
}
}
....
buildTypes {
debug {
ndk {
abiFilters "armeabi-v7a", "arm64-v8a", "x86", "x86_64"
}
FirebasePerformance {
instrumentationEnabled false
}
}
release {
minifyEnabled true
useProguard = true
proguardFile getDefaultProguardFile('proguard-android.txt')
proguardFile 'proguard-rules.pro'
ndk {
abiFilters "armeabi-v7a", "arm64-v8a", "x86_64"
}
/* Add the firebaseCrashlytics extension (by default,
* it's disabled to improve build speeds) and set
* nativeSymbolUploadEnabled to true. */
firebaseCrashlytics {
nativeSymbolUploadEnabled true
}
}
}
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
}
// Upload Crashlytics NDK symbols
tasks.whenTaskAdded { task -> if (task.name.startsWith('assemble') && task.name.endsWith("Release")) task.finalizedBy "uploadCrashlyticsSymbolFile" + task.name.substring('assemble'.length()) }
dependencies {
implementation fileTree(include: ['*.jar', '*.aar'], dir: 'libs')
implementation platform('com.google.firebase:firebase-bom:25.2.1')
implementation "com.google.firebase:firebase-crashlytics-ndk:17.0.0"
implementation 'com.google.firebase:firebase-iid'
implementation 'com.google.firebase:firebase-messaging'
implementation 'com.google.firebase:firebase-appindexing'
implementation 'com.google.firebase:firebase-analytics'
implementation 'com.google.firebase:firebase-perf'
...
}
apply plugin: 'com.google.gms.google-services'
通过Firebase控制台报告的崩溃很多,就像我捕获的一样。它们中没有一个具有适当的可用回溯。
任何提示,如果没有框架,本机报告当前都是无用的。
我已经基于Kevin's answer解决了已压缩和未剥离的本机lib目录,如下所示:
android {
...
buildTypes {
...
release {
firebaseCrashlytics {
nativeSymbolUploadEnabled true
applicationVariants.all { variant ->
firebaseCrashlytics {
strippedNativeLibsDir "build/intermediates/stripped_native_libs/${variant.name}/out/lib"
unstrippedNativeLibsDir "build/intermediates/ndkBuild/${variant.name}/obj/local"
}
}
}
}
}
}
并且设法产生了一个崩溃,该崩溃具有一个通过我自己的本机库访问的调用栈,但是问题仍然存在:
[按照Kevin的建议,我使用此命令调试符号文件的上载问题(由于我在Windows上,所以我使用find /I
而不是grep
:]
gradlew app:assembleRelease --console=plain --debug | find /I "[com.google.firebase.crashlytics]"
并且结果证明,将implementation 'com.google.firebase:firebase-iid'
与implementation platform('com.google.firebase:firebase-bom:25.2.1')
一起使用才使我无法赎回:),因为显然Firebase已经在com.google.firebase:firebase-messaging
本身内部使用了实例ID依赖项。长话短说,仅使用此配置可以帮助我正确上传符号:
android {
...
buildTypes {
...
release {
firebaseCrashlytics {
nativeSymbolUploadEnabled true
}
}
}
}
// Upload Crashlytics NDK symbols
tasks.whenTaskAdded { task -> if (task.name.startsWith('assemble') && task.name.endsWith("Release")) task.finalizedBy "uploadCrashlyticsSymbolFile" + task.name.substring('assemble'.length()) }
dependencies {
...
implementation platform('com.google.firebase:firebase-bom:25.2.1')
implementation 'com.google.firebase:firebase-iid:20.1.5'
implementation 'com.google.firebase:firebase-messaging'
...
}
至少要在我自己的本地库中获得调用堆栈:
Firebaser here-
看来您粘贴了此屏幕快照的此崩溃报告仅在系统库中发生。我们可以在Crashlytics崩溃报告(和墓碑)中看到,所有堆栈帧都与“ libc.so”相关联-这是一个Android系统运行时库,并且像Crashlytics这样的任何库都无法符号化。
这是因为Crashlytics只能符号化来自您为其上传符号的库的崩溃或堆栈框架。而且由于libc.so是一个系统库,您和Crashlytics都没有该库的符号,所以这是预期的行为。 Crashlytics仍会显示框架,即使它不能只是象征性的,因此它仍在报告尽可能多的信息。
[如果您能够提交测试崩溃报告,且该报告的调用堆栈经过您自己的本机库,而您要为其尝试上载符号,而到处仍然看到“(Missing)”,那将是意外。如果是这种情况,建议您确保已遵循链接文档中的these instructions,如果仍有问题,请联系Firebase support。