Firebase Crashlytics未在控制台仪表板swift中显示崩溃报告

I have setup all these steps and bundel id on Firesbase Dashboard and tried crash many times but not getting any report.

我已经在Firesbase Dashboard上设置了所有这些步骤和bundel id，并尝试多次崩溃但没有收到任何报告。

pod 'Firebase/Core' pod 'Fabric', '~> 1.7.2' pod 'Crashlytics', '~> 3.9.3'
pod'Firebase / Core'pod'Fabric'，'〜> 1.7.2'pod'Crashlytics'，'〜> 3.9.3'
In Build phase added run Script : "${PODS_ROOT}/Fabric/run"
在Build阶段添加了运行脚本：“$ {PODS_ROOT} / Fabric / run”
Debug Inforation Format : DWARF with dSYM File
调试信息格式：带有dSYM文件的DWARF
running in simulator with following steps

通过以下步骤在模拟器中运行
- (IBAction)crashButtonTapped:(id)sender { [[Crashlytics sharedInstance] crash]; }
  
  （IBAction）crashButtonTapped：（id）sender {[[Crashlytics sharedInstance] crash]; }
- Click play_arrow Build and then run the current scheme in Xcode to build your app on a device or simulator.
  
  单击play_arrow Build然后在Xcode中运行当前方案以在设备或模拟器上构建您的应用程序。
- Click stop Stop running the scheme or action in Xcode to close the initial instance of your app. This initial instance includes a debugger that interferes with Crashlytics.
- 单击停止在Xcode中停止运行方案或操作以关闭应用程序的初始实例。此初始实例包含一个干扰Crashlytics的调试器。
- Open your app again from the simulator or device. Touch Crash to crash the app.
- 再次从模拟器或设备打开您的应用程序。触摸崩溃以使应用崩溃。

3 个解决方案

#1

I took the same steps as you and thought I had an issue until I realized there's a delay for the crashes to show up on the console. In my case it took about 40 minutes to appear.

我采取了与你相同的步骤，并认为我有一个问题，直到我意识到崩溃出现在控制台上的延迟。在我的情况下，它花了大约40分钟出现。

Here's a blog post about it.

这是关于它的博客文章。

#2

Firebase Crashlytics未在控制台仪表板swift中显示崩溃报告 Check run script only when installing

仅在安装时检查运行脚本

#3

I did everything on stack overflow my upload was successful but nothing showed up. After trying to figure out the solution I tried this and it worked for me as well as for some other people facing the same issue, might help others who end up here.

我在堆栈溢出上做了一切，我的上传成功但没有出现。在试图找出解决方案之后，我尝试了这个并且它对我和其他一些面临同样问题的人都有用，可能会帮助其他人来到这里。

I posted it in issues section check it out https://github.com/firebase/quickstart-ios/issues/413

我发布在问题部分检查出来https://github.com/firebase/quickstart-ios/issues/413

One thing that I did was to move my test crash

我做的一件事是移动我的测试崩溃

Crashlytics.sharedInstance().crash()

to the first view controller e.g WelcomeViewController and then after the crash I closed and opened my app again. Then just waited for sometime and it appeared.

到第一个视图控制器，例如WelcomeViewController然后在崩溃后我关闭并再次打开我的应用程序。然后等了一段时间才出现了。

Before doing all of that my test crash was within a view controller which was part of a tabBarController as it wasn't the top most view controller maybe that's what caused the issue. After my first crash appeared on the firebase console then my other crashes started appearing.

在完成所有这些操作之前，我的测试崩溃是在一个视图控制器中，它是tabBarController的一部分，因为它不是最*的视图控制器，也许是造成这个问题的原因。在我的第一次崩溃出现在firebase控制台后，我的其他崩溃开始出现。

#1