我按照Firebase / Crashlytics上的说明进行操作，但我无法使崩溃显示在控制台中。在某个时间点，它确实起作用了，但现在却没有。
这是崩溃后最近一次尝试上传的控制台输出。
2018-12-13 19:18:13.145000-0800 MyApp[599:21332] 4.8.1 - [Firebase/Analytics][I-ACS036002] Firebase screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
file log added: true
2018-12-13 19:18:13.209647-0800 MyApp[599:21335] 4.8.1 - [Firebase/Core][I-COR000001] Configuring the default app.
2018-12-13 19:18:13.221188-0800 MyApp[599:21269] [Fabric] [Crashlytics] This version of FIRApp does not support isDataCollectionDefaultEnabled. Ignoring.
2018-12-13 19:18:13.221338-0800 MyApp[599:21269] [Fabric] [Crashlytics] This version of FIRApp does not support isDataCollectionDefaultEnabled. Ignoring.
2018-12-13 19:18:13.221364-0800 MyApp[599:21269] [Fabric] [Crashlytics] This version of FIRApp does not support isDataCollectionDefaultEnabled. Ignoring.
2018-12-13 19:18:13.221395-0800 MyApp[599:21269] [Crashlytics] Version 3.12.0 (136)
2018-12-13 19:18:13.221478-0800 MyApp[599:21269] [Crashlytics] Running on iPhone8,4, 11.4.1 (15G77)
2018-12-13 19:18:13.230209-0800 MyApp[599:21269] [Crashlytics:Crash:Reports:Event] Registered Firebase Analytics event listener
2018-12-13 19:18:13.235577-0800 MyApp[599:21341] [Fabric] [Crashlytics] This version of FIRApp does not support isDataCollectionDefaultEnabled. Ignoring.
2018-12-13 19:18:13.243302-0800 MyApp[599:21269] [Answers] Initialized
2018-12-13 19:18:13.289486-0800 MyApp[599:21269] [Fabric] [Crashlytics] This version of FIRApp does not support isDataCollectionDefaultEnabled. Ignoring.
2018-12-13 19:18:13.297664-0800 MyApp[599:21269] [Fabric] Initialized with kit versions: {
"com.twitter.answers.ios" = "1.4.0";
"com.twitter.crashlytics.ios" = "3.12.0";
"io.fabric.sdk.ios" = "1.9.0";
}
2018-12-13 19:18:13.352472-0800 MyApp[599:21341] [Crashlytics:Crash:Reports] Packaged report with id 'fb37c35c9185406b9bd72acc10709fb4' for submission
2018-12-13 19:18:13.353865-0800 MyApp[599:21341] [Crashlytics:Crash] Unable to read identifier at path *SOMEPATH**
2018-12-13 19:18:13.364756-0800 MyApp[599:21341] [FileManager] Failed to remove file '(null)' : (null)
2018-12-13 19:18:13.365267-0800 MyApp[599:21341] [Crashlytics:Crash:Reports] Unable to remove a processing item
2018-12-13 19:18:13.365617-0800 MyApp[599:21341] [Crashlytics:Crash:Reports] Packaged report with id '(null)' for submission
2018-12-13 19:18:13.428401-0800 MyApp[599:21269] [Fabric] [Fabric +with] called multiple times. Only the first call is honored, please pass all kits you wish to initialize
Documents: file:///var/mobile/Containers/Data/Application/841A117D-7E43-4CD7-AEF6-2EB205E18B84/Documents/
Database Directory: /var/mobile/Containers/Data/Application/841A117D-7E43-4CD7-AEF6-2EB205E18B84/Library/Application Support/storage.sqlite
2018-12-13 19:18:13.463439-0800 MyApp[599:21335] 4.8.1 - [Firebase/InstanceID][I-IID013010] InstanceID library version 2.0.10
2018-12-13 19:18:13.470649-0800 MyApp[599:21340] 4.8.1 - [Firebase/Analytics][I-ACS024000] Debug mode is on
2018-12-13 19:18:13.470905-0800 MyApp[599:21340] 4.8.1 - [Firebase/Analytics][I-ACS005000] The AdSupport Framework is not currently linked. Some features will not function properly. Learn more at somegoogleURL
2018-12-13 19:18:13.495759-0800 MyApp[599:21269] NO CHANGES IN ** MagicalRecord Default Context ** CONTEXT - NOT SAVING
1136.0
从日志中可以看到，上载报告时遇到了麻烦，我不知道为什么。
以下是我的应用程序历史记录的简短摘要，最初是使用Fabric.io，然后移至Firebase / Crash，然后移至Firebase / Crashlytics。这是我已经尝试过的。
我检查了脚本，以确保我正确上传了dSym，并说确实如此。 upload-symbols[65786:2975450] Successfully submitted symbols for architecture arm64 with UUID Some UUID in dSYM: myApp.app.dSYM
我遍历了构建阶段示例，以设置crashlytics，看起来不错
在我的控制台中，我没有看到以下消息
[Crashlytics:Crash] report submission successful
和其他用户一样，尽管我相信我很久以前就曾经这样做过。
[更新]我确实已经从构建脚本和info.plist中删除了Fabric.io密钥。
[更新]在更仔细地阅读了说明之后，我注意到上述控制台信息实际上是成功上传的信息。我知道这是因为出现了崩溃，并且时间戳与日志匹配。要查看崩溃是如何在Firebase控制台中正确显示的，请查看答案。
答案 0 :(得分：0)
昨天我遇到了同样的问题，自己解决了。
我已经通过集成从Fabric Crashlitics迁移到Firebase。过了一会儿，我决定完全迁移到Firebase Crashlytics。
Build Script。只能"${PODS_ROOT}/Fabric/run" 没有任何键，它在Fabric中的状态如何。 （如果您使用的是Xcode 10，还必须指定输入文件）Fabric中删除Info.plist键，否则Fabric的脚本会显示有关键丢失的错误。希望能为您提供帮助。
答案 1 :(得分：0)
好的，我想说我是个白痴。我要做的就是按照指示进行。因此，为使像我这样的白痴进一步陷入困境，这是您必须做的事情才能使崩溃正确显示。