xCode 9.3和Firebase Crashlytics无法正常工作 [英] xCode 9.3 and Firebase Crashlytics not working
问题描述
我无法让Firebase Crashlytics显示我的xCode iOS Swift应用程序崩溃。
I cannot get Firebase Crashlytics to show my crashes of my xCode iOS Swift app.
- 使用xCode 9.3
- 我已经手动（不使用cocoapods）集成了Crashlytics SDK
，如下所示：
https://firebase.google.com/docs/crashlytics/get-started?authuser=0 - I在模拟器和设备上都进行了测试
- 我都崩溃了（使用了自己编写的崩溃函数，还使用了提供的崩溃函数），我重新启动了设备/模拟器（因为崩溃仅在下次启动时传输）
- 我在Firebase Crashlytics控制台中没有看到任何崩溃，它一直说升级到Crashlytics以获得更强大的实时崩溃分析
- 我可以在xcode调试控制台日志中确认crashlytics正在运行，因为我看到 [Crashlytics]版本3.10.1（129）
- 我禁用了位码不会改变任何东西...
- 我在系统控制台中查看并发现：
- Using xCode 9.3
- I have manually (not using cocoapods) integrated the Crashlytics SDK as specified here: https://firebase.google.com/docs/crashlytics/get-started?authuser=0
- I have tested both in the simulator and on the device
- I made both crash (using an own written crash function, but also the supplied crash function), I restarted the device/simulator (because the crash is only transmitted upon the next launch)
- I am not seeing any crashes in the Firebase Crashlytics console, it keeps on saying "Upgrade to Crashlytics for more powerful, realtime crash analysis"
- I can confirm in the xcode debug console logs that the crashlytics is running because I see "[Crashlytics] Version 3.10.1 (129)"
- I disabled bitcode does not change anything...
- I looked in the system console and found:
默认值21：17：49.828801 +0200 nsurlsessiond [9
report.crashlytics.com:443流，pid：72896，流量类别：200，
tls，无限期]取消了
[9.1 463924B9-A95E-44FB-AA19-CFE9616E37E0 192.168.99.209.59507<-> 54.243.248.96:443]
连接路径：满意（路径满意），接口：en0
持续时间：2.586s，DNS @ 0.000s花了0.027s，TCP @ 0.028s花了0.110s，TLS花了0.255s
字节输入/输出：6086/30045，数据包入/ out：7/23，rtt：0.092s，重传的数据包：0，乱序数据包：0
default 21:17:49.828801 +0200 nsurlsessiond [9 reports.crashlytics.com:443 stream, pid: 72896, traffic class: 200, tls, indefinite] cancelled [9.1 463924B9-A95E-44FB-AA19-CFE9616E37E0 192.168.99.209.59507<->54.243.248.96:443] Connected Path: satisfied (Path is satisfied), interface: en0 Duration: 2.586s, DNS @0.000s took 0.027s, TCP @0.028s took 0.110s, TLS took 0.255s bytes in/out: 6086/30045, packets in/out: 7/23, rtt: 0.092s, retransmitted packets: 0, out-of-order packets: 0
- 好像9个崩溃正在等待/挂起？
- 我想这是什么原因，也许是因为没有上载dsym，所以我在xCode中检查了构建过程并发现：
- 以验证模式启动的上传器是什么意思？
- 我想使用以下命令手动上传dsym： https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?authuser=0 ，但fabric.framework确实可以不包含任何上传符号？ Google文档错了吗？我可以看到一个 uploadDSYM，但这并没有接缝具有相同的选项/参数，所以我想它不是这个... /？
- What does this "launched uploader in validation mode" mean? Does it mean that the dsym upload is not working?
- I wanted to manually upload the dsyms using : https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?authuser=0 but the fabric.framework does not contain any upload-symbols? The Google documentation wrong? I can see an "uploadDSYM" but this does not seam to have the same options/arguments so I guess its not this one...?
2018-04-16 21：55：35.270 uploadDSYM [77897：3132594] Fabric.framework / run
1.7.0（208）2018 -04-16 21：55：35.278 uploadDSYM [77897：3132594]检测到Firebase模式。 2018-04-16 21：55：35.278 uploadDSYM [77897：3132594]使用
API密钥： xxxxxxxxxxxxxxxxxx 2018-04-16 21：55：35.279
uploadDSYM [77897：3132594]在以下位置启动了上传器验证模式
2018-04-16 21:55:35.270 uploadDSYM[77897:3132594] Fabric.framework/run 1.7.0 (208) 2018-04-16 21:55:35.278 uploadDSYM[77897:3132594] Firebase mode detected. 2018-04-16 21:55:35.278 uploadDSYM[77897:3132594] Using API Key: "xxxxxxxxxxxxxxxxxx" 2018-04-16 21:55:35.279 uploadDSYM[77897:3132594] Launched uploader in validation mode
推荐答案
基于Todd的输入（他来自Crashlytics），我发现了问题所在。
原因是在Firebase控制台中为该应用程序指定的bundleid不是我在实际应用程序中使用的那个！因此，我删除了旧应用（具有错误的捆绑软件ID），并在Firebase控制台中使用正确的捆绑软件ID重新创建了它，现在它可以正常工作。
Based on Todd's input (he is from Crashlytics) I found the issue. The reason was that the bundleid specified in the Firebase Console for the app was not the one that I was using in the actual app! So I deleted the old app (with the wrong bundle id) and re-created it with the correct bundleid in the Firebase Console and now its working.
注意：显然，一旦创建了应用，就无法更改bundleid。
这篇关于xCode 9.3和Firebase Crashlytics无法正常工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
