TL;DR: run 100 for Crashlytics to begin working properly, assuming you've set everything up correctly (which it certainly appears you have since 101 is crashing your application.)
Please note - in order for 101 to function properly, you will have needed to configure your APK for release builds according to the directions here: 100
PROOF OF CRASHLYTICS PROPERLY REPORTING AS OF THE WRITING OF THIS ANSWER.我从未如此高兴地看到我的无故障用户评分下降:)
如果你有任何问题,请告诉我!设置签名可能会有点混乱,所以如果您有任何问题,请告诉我.
这是一个非常令人沮丧的问题,但幸运的是,我找到了解决方案,我和你们处境完全相同.
看到那个红色的大屏幕了吗?这就是React Native在开发过程中告诉你你犯了某种错误的方式.不明显的是,这个红色屏幕阻止错误进入我们的错误报告工具.在发布模式下运行应用程序将防止React Native显示红色屏幕,并且您的错误报告工具将能够报告崩溃.
由于Gian有pointed out in another answer to this question,个,firebase.crashlytics().crash()
似乎不能正常工作.然而,事实并非如此.无论何时在调试模式下操作(只要你看到红色屏幕,你就处于我所说的调试模式),Crashlytics和其他崩溃报告工具都无法捕获本机异常,但它们可以捕获Javascript异常.