Firebase crashlytics不报告崩溃 [英] Firebase crashlytics not reporting crash

问题描述

我正在从Fabric升级到Firebase crashlytics。我已将Firebase和Fabric / Crashlytics窗格添加到我的项目中，并添加了.plist等。一切似乎都工作正常，但没有报告崩溃。我正在使用 assert（！故意崩溃以测试crashlytics）; 生成崩溃，因为我看到其他人提到了 [[Crashlytics sharedInstance]崩溃] 不适用于他们。

I'm upgrading from Fabric to Firebase crashlytics. I've added Firebase and Fabric/Crashlytics pods to my project, added the .plist etc. All seems to be working fine, except crashes are not being reported. I'm generating a crash using assert(! "crashing on purpose to test crashlytics"); as I saw someone else mention [[Crashlytics sharedInstance] crash] didn't work for them.

有趣的是我使用的内部版本号的无崩溃用户生成崩溃后的结果为0％，但崩溃报告为0。dSYMs选项卡未列出版本号。

What's interesting is the 'crash free users' for the build number I'm using drops to 0% after the crash is generated, but crashes is reported as 0. The dSYMs tab doesn't list the version number.

在这里，当将 -FIRDebugEnabled 作为参数传递时，调试视图上会发生崩溃：

Here's the crash coming through on the debug view when -FIRDebugEnabled is passed as an argument:

有任何建议吗？

推荐答案

从迁移时，我遇到了类似的问题从Fabric到Firebase Crashlytics。您不应遵循Firebase网站上的说明。遵守@Ashvini提到的面料说明。我假设您在迁移到Firebase之前已经使Crashlytics正常运行。我测试了这种方法，它对我有用。
这很痛苦，因为新旧项目将采用不同的Crashlytics实现。

I had a similar issue when migrating from Fabric to Firebase Crashlytics. You should not follow the Firebase website instructions. Stick with the Fabric instructions as mentioned by @Ashvini. I am assuming that you already had Crashlytics working fine before migration to Firebase. I tested this approach and it works for me. This is a pain as older and newer projects will have different Crashlytics implementations.

这篇关于Firebase crashlytics不报告崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！