问题描述
我已经对应用程序实施了Firebase / Crashlytics。我在日志中看到该应用正在发送崩溃。 Firebase控制台不显示任何内容。我可以看到实施后无崩溃用户数量有所减少。控制台未显示任何内容。请帮忙。我的应用程序ID：com.obssmobile.mychesspuzzlegame
I have implemented Firebase/Crashlytics to an app. I can see in the logs that app is sending crashes. Firebase Console doesn't show anything. I can see crash free user count decreased after the implementation. Console doesn't show up anything. Please help. My app ID: com.obssmobile.mychesspuzzlegame
我已经断开了Xcode调试器的连接，重新启动了该应用程序并重新制作了当机。问题仍然存在。
在这里我可以看到无崩溃用户开始下降。
Here I can see that crash free users started dropping.
在这里我可以看到报告提交成功日志
Here I can see "report submission successful" log
控制台在几个小时后没有更新。
Console is not updated after several hours.
推荐答案
对于从Fabric迁移的，已删除并与Firebase重新集成的应用程序，有时存在链接问题后端可能导致您的应用进入Firebase侦听器无法进行正确设置请求的状态，从而无法使用新的SDK登载您的应用。在这种情况下，当前有两种解决方法。
For apps migrated from Fabric that have been deleted and reintegrated with Firebase, sometimes a linking issue in the backend can cause your app to go into a state where the Firebase listener is unable to make the correct settings request to onboard your app using the new SDK. In these situations there are currently two workarounds.
-
删除您的应用，然后使用新的捆绑包ID或在
Delete your app, and reonboard with either a new bundle ID or using the same bundle ID in a different Firebase Project.
写入Firebase支持，他们可以尝试手动删除导致此问题的后端链接。但是，只有在您需要保留大量历史崩溃数据时，才应该这样做。
Write in to Firebase support and they can try to manually delete the backend link that's causing this issue. However, this should only be done if you have a lot of historical crash data that you need to preserve.
这篇关于旧的Fabric应用程序不会在新的Firebase实施中显示崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！