Firebase Crashlytics Android NDK:崩溃报告上的空符号 [英] Firebase Crashlytics Android NDK: empty symbols on crash reports
问题描述
我在Android Studio中有一个包含Android Java服务的项目，该项目通过JNI调用使用某些本机库.
I have a project in Android Studio that consist on Android Java Services that uses some native libraries through JNI calls.
基本上，我有2个库可以编译，而另一个库是预编译的，因此我无法访问源代码.由于预编译的库仅针对armeabi-v7a构建，因此我有一个abiFilter.
Basically, I have 2 libraries I compile and another library that is precompiled, so I don't have access to the source code. As the precompiled library is only built for armeabi-v7a, I have an abiFilter.
在这里，我的/build.gradle
Here, my /build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
maven { url 'https://maven.fabric.io/public' }
}
dependencies {
classpath 'com.android.tools.build:gradle:3.5.2'
classpath 'io.fabric.tools:gradle:1.31.2'
classpath 'com.google.gms:google-services:4.3.3' // Google Services plugin
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
和我的/app/build.gradle(省略了明智的代码)
and my /app/build.gradle (omitted the sensible code)
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'
def enableCrashlyticsNdk = true
repositories {
jcenter()
maven { url 'https://maven.fabric.io/public' }
}
android {
signingConfigs {
platformSignature {
keyAlias "${platform_keystore_alias}"
keyPassword "${platform_keystore_password}"
storeFile file("${platform_keystore_path}")
storePassword "${platform_keystore_password}"
}
}
compileSdkVersion 29
buildToolsVersion "29.0.2"
lintOptions {
abortOnError false
}
defaultConfig {
applicationId com.example.stackoverflowapp
minSdkVersion 26
targetSdkVersion 28
versionCode 1
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
externalNativeBuild {
cmake {
cppFlags "-std=c++11 -Werror"
}
}
ndk {
// Specifies the ABI configurations of your native
// libraries Gradle should build and package with your APK.
abiFilters 'armeabi-v7a'
}
}
buildTypes {
release {
minifyEnabled true
jniDebuggable false
proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
signingConfig signingConfigs.platformSignature
}
debug {
debuggable true
jniDebuggable true
versionNameSuffix = " (debug)"
signingConfig signingConfigs.platformSignature
}
}
android.applicationVariants.all { variant ->
variant.outputs.all {
outputFileName = buildOutputName(variant)
}
}
packagingOptions {
exclude 'jsr305_annotations/Jsr305_annotations.gwt.xml'
exclude 'error_prone/Annotations.gwt.xml'
exclude 'third_party/java_src/error_prone/project/annotations/Annotations.gwt.xml'
exclude 'third_party/java_src/error_prone/project/annotations/Google_internal.gwt.xml'
}
externalNativeBuild {
cmake {
path "src/main/cpp/CMakeLists.txt"
version "3.10.2"
}
}
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
}
ext {
appCompatVersion = '28.0.0'
}
crashlytics {
enableNdk enableCrashlyticsNdk
}
tasks.whenTaskAdded { task ->
if (enableCrashlyticsNdk && task.name.startsWith('assemble')) {
task.finalizedBy "crashlyticsUploadSymbols" + task.name.substring('assemble'.length())
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'androidx.recyclerview:recyclerview:1.0.0'
implementation 'androidx.leanback:leanback:1.0.0'
implementation 'androidx.appcompat:appcompat:1.0.0'
implementation 'com.google.android.exoplayer:exoplayer:r1.5.14'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'androidx.test.ext:junit:1.1.1'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0'
implementation 'com.google.code.gson:gson:2.8.5'
implementation 'com.google.firebase:firebase-analytics:17.2.1'
implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
implementation 'com.crashlytics.sdk.android:crashlytics-ndk:2.1.1'
}
apply plugin: 'com.google.gms.google-services' // Google Play services Gradle plugin
由于我的应用是Android系统的一部分，因此已使用平台签名对其进行了签名.
As my app is part of the Android system, it is signed with a platform signature.
我用CMake编译我的2个库.
I compile my 2 libraries with CMake.
我已按照Firebase网站上的所有步骤进行操作:
I have followed all steps from the firebase web:
- https://firebase.google.com/docs/android/setup
- https://firebase.google.com/docs/crashlytics/get-started?platform = android
- https://firebase.google.com/docs/crashlytics/ndk-reports
- https://firebase.google.com/docs/android/setup
- https://firebase.google.com/docs/crashlytics/get-started?platform=android
- https://firebase.google.com/docs/crashlytics/ndk-reports
我在一个库中有意添加了崩溃，当应用崩溃时，The Crashlytics收集了崩溃并成功上传了崩溃报告.
I've added a crash intentionally within one of my libraries and when the app reaches crash, The Crashlytics gathered the crash and upload the crash report successfully.
CrashlyticsCore: Crashlytics report upload complete: 5DE66A450116-0001-1A8B-A3EE77BA9366
然后，当我进入Firebase控制台时，我看到所有堆栈帧都(丢失)
Then, when I go to the firebase console, I see that all stack frames are (missing)
Crashed: Thread #1
SIGSEGV 0x0000000000000028
-------------------------------------------
0 MyApp.apk (Missing)
1 libart.so (Missing)
2 (Missing)
3 (Missing)
4 (Missing)
5 (Missing)
6 (Missing)
7 libart.so (Missing)
8 libart.so (Missing)
9 libart.so (Missing)
10 (Missing)
11 libart.so (Missing)
12 (Missing)
查看Crashlytics构建日志，看来cSym文件已正确上传.
Reviewing the Crashlytics build logs, it seems like the cSym files are uploaded properly.
[DEBUG] (Execution worker for ':' Thread 6) com.crashlytics - cSYM file(s) uploaded.
我不确定该符号是否已正确创建和上传，或者该设备创建的崩溃报告是否存在问题.我担心这个问题与Android权限有关，因为我的应用程序是系统应用程序.
I'm not really sure if the symbols are properly created and uploaded or if there is an issue with the crash reports created by the device. I'm afraid of the problem would be related with android permissions as my app is a system app.
我想我已经阅读了所有与Crashlytics和NDK相关的stackoverflow帖子.另外，我还用Google搜索了与"crashlytics，ndk和符号"有关的任何组合.
I guess I've read all the stackoverflow posts related with Crashlytics and NDK. Also, I've also googled any kind of combination related with "crashlytics, ndk and symbols".
最后，我正在使用的工具版本:
Finally, the tool versions I'm using:
- Android Studio:3.5.1
- 等级:5.4.1
- Gradle插件:3.5.2
- 织品gradle插件:1.31.2
非常感谢您.
推荐答案
您可能要考虑升级到新的(非结构)Crashlytics SDK.据推测，它是架构的替代路线.
You may want to consider upgrading to the new (non fabric) Crashlytics SDK. It is, assumedly, the roadmap replacement for fabric.
https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform = android
和
https://firebase.google.com/docs/crashlytics/ndk-reports-new-sdk
尽管在撰写本文时它处于Beta版，但我最近相当轻松地将其转换为它.在此过程中，我还可以停止在本机代码中使用结构本机库(libCrashlytics)及其标头.
While it is in Beta as of this writing, I recently converted to it fairly easily. In the process I was also able to stop using the fabric native library (libCrashlytics) and its header in my native code.
此外，请确保在构建过程中将符号正确上传到Firebase/Fabric.您可能需要在afterEvaluate块的一部分中明确地执行此操作，如下所示:
Additionally, ensure you are properly uploading the symbols to Firebase / Fabric as part of your build process. You may need to do this explicitly as part of an afterEvaluate block like so:
afterEvaluate {
if (gradle.startParameter.taskNames.contains(":app:assemble<Flavor><BuildType>")) {
assemble<Flavor><BuildType>.finalizedBy(uploadCrashlyticsSymbolFile<Flavor><BuildType>)
}
}
请确保将<Flavor>和<BuildType>替换为在productFlavors和buildTypes块中定义的风味和构建类型.
Be sure to replace <Flavor> and <BuildType> with the flavor and build type(s) you defined in your productFlavors and buildTypes blocks.
例如，以下风味/构建类型:
For example, the below flavor / build types:
buildTypes {
release {
signingConfig signingConfigs.release
buildConfigField "boolean", "RELEASE", "true"
shrinkResources true
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
}
debug {
buildConfigField "boolean", "RELEASE", "false"
applicationIdSuffix '.debug'
versionNameSuffix '-DEBUG'
ext.alwaysUpdateBuildId = false
crunchPngs false
}
}
flavorDimensions "all"
productFlavors {
fat {
ndk {
abiFilters "x86_64", "x86", "arm64-v8a", "armeabi-v7a"
}
dimension "all"
}
}
将最终导致需要使用uploadCrashlyticsSymbolFileFatDebug和uploadCrashlyticsSymbolFileFatRelease任务完成的assembleFatDebug和assembleFatRelease任务.
would result in assembleFatDebug and assembleFatRelease tasks that you'd need to finalize with uploadCrashlyticsSymbolFileFatDebug and uploadCrashlyticsSymbolFileFatRelease tasks accordingly.
注意:
如果您仍在使用Fabric，则要用来完成assemble*任务的任务是crashlyticsUploadSymbols<Flavor><BuildType>.
NOTE:
If you are still using Fabric, the task you want to finalize your assemble* task with is crashlyticsUploadSymbols<Flavor><BuildType>.
这篇关于Firebase Crashlytics Android NDK:崩溃报告上的空符号的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
