Crashlytics在仪表板中未显示崩溃

Crashlytics在仪表板中未显示崩溃

本文介绍了iOS Firebase Crashlytics在仪表板中未显示崩溃的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在iOS应用中实现了Firebase Crashlytics.我遵循了Firebase文档中的所有步骤.我已经在没有调试器的情况下通过先关闭应用程序然后再重新运行该应用程序来运行崩溃解析程序,以便可以发送崩溃报告.我什至收到此消息

I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message

我什至还添加了运行脚本,并将变量设置为带有DSYM的DWARF"

I even added the Run script and set variable to "DWARF with DSYM"

我准备在某个地方准备就绪,即使没有成功上传DSYM,也不会看到崩溃.因此,我进入了pods/Fabric/,然后单击运行" CLI.它明确指出由于未找到GoogleServiceInfo.plist而未上传DSYM .尽管它在那里,是的,它包含在我的目标以及我的捆绑包中.

I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully. So I went into my pods/Fabric/ and click on "run" CLI. It clearly says DSYM not uploaded because GoogleServiceInfo.plist wasn't found. Although it's there and yes it's included in my target as well as in my bundle.

这是屏幕截图.我已经尝试了所有可能的步骤以包含GoogleService-Info.plist,但仍然在手动运行时显示了这一点.

Here is the screenshot. I have tried all possible steps to include GoogleService-Info.plist but still when I run manually it says this.

还有什么我可以尝试的吗?

Any another thing that I can try ?

推荐答案

对于仍然为这个问题苦苦挣扎的人来说,这是为我解决问题的方法.

To someone still struggling with the issue here is what resolved the issue for me.

  1. 我删除了GoogleService-Info.plist并再次添加了它.

  1. I deleted the GoogleService-Info.plist and added it again.

我在欢迎屏幕上尝试了崩溃,而不是在其中一个我相信标签栏控制器的屏幕无法启动找到可以正常使用的GoogleServiceInfo.plist文件.

I tried the crash on my welcome screen rather than in one of the screens of my tab bar controller as I believe from there it's unable to find GoogleServiceInfo.plist file so it worked.

这篇关于iOS Firebase Crashlytics在仪表板中未显示崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-01 00:13