简体   繁体   English

Firebase Crashlytics 在从结构迁移后不会跟踪 Android 的崩溃

[英]Firebase Crashlytics doesn't tracking the crash for Android after migration from fabric

I am developing an android app in a company.我正在一家公司开发 android 应用程序。

This app has used the Fabric library.这个应用程序使用了 Fabric 库。

I can find the dependencies in the 'build.gradle' files.我可以在“build.gradle”文件中找到依赖项。

And we could see the crash report in our Firebase Crashlytics console.我们可以在 Firebase Crashlytics 控制台中看到崩溃报告。

Recently, I changed the dependencies from the Fabric to Firebase Crashlytics.最近,我将依赖项从 Fabric 更改为 Firebase Crashlytics。

// Remove the Fabric Crashlytics SDK.
implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'

// Add the Firebase Crashlytics SDK.
implementation 'com.google.firebase:firebase-crashlytics:17.1.1'

And I followed the migration guide documents.我遵循了迁移指南文件。

Building the signing Apk success.构建签名 Apk 成功。

And I upload the APK into the PlayStore yesterday.我昨天将 APK 上传到了 PlayStore。

Today morning, when I check the Firebase Crashlytics console.今天早上,当我检查 Firebase Crashlytics 控制台时。

There were no crash reports related to the new version of APK.没有与新版 APK 相关的崩溃报告。 (I couldn't find only old version's crash reports.) (我找不到旧版本的崩溃报告。)

But when I check it on PlayStore console, I can find some crash reports.但是当我在 PlayStore 控制台上查看它时,我可以找到一些崩溃报告。

What should I do now?我现在该怎么办?


When I run it on debug mode, I can find below logs.当我在调试模式下运行它时,我可以在下面找到日志。

2020-08-13 12:35:31.568 709-709/co.spoonme I/FirebaseCrashlytics: Initializing Crashlytics 17.1.1

And when I check the "Firebase > Latest Release" tab, I can find the new version.当我检查“Firebase > 最新版本”选项卡时,我可以找到新版本。 This means that the new version is tracked by Firebase.这意味着新版本被 Firebase 跟踪。

But only crash reports are not tracked... why......但是只有崩溃报告没有被跟踪……为什么……

Firebaser here - Firebaser在这里-

Make sure that you've followed all the instructions in the migration guide , in case there are any old dependencies or things that you've accidentally left behind.确保您已遵循迁移指南中的所有说明,以防有任何旧的依赖项或您不小心留下的东西。

If you're still not able to get crash reports after creating and forcing a test crash , try enabling debug mode and forcing another test crash.如果您在创建并强制测试崩溃后仍然无法获得崩溃报告,请尝试启用调试模式并强制另一个测试崩溃。 After you relaunch, there should be some more logging in your logcat that tells you more about the state of Firebase initialization, and if the crash report has been successfully uploaded.重新启动后,您的 logcat 中应该会有更多日志记录,告诉您有关 Firebase 初始化的 state 的更多信息,以及崩溃报告是否已成功上传。 If you're okay with sharing the logs, it would be a good idea to update your post with those logs for visibility.如果您同意共享日志,最好使用这些日志更新您的帖子以提高可见性。

I think it would also be helpful to see your build.gradle files and where you're initializing Firebase in your main app code.我认为查看您的 build.gradle 文件以及您在主应用程序代码中初始化 Firebase 的位置也会有所帮助。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM