简体   繁体   English

iOS-Crashlytics缺少dSYM来处理崩溃

[英]iOS - Crashlytics missing dSYMs to process crashes

I know this is a frequently asked question. 我知道这是一个常见问题。

I just spent the entire day looking for answers, without success. 我整整一天都在寻找答案,但没有成功。

Here are the different posts that helped me, but didn't fix my issue. 以下是对我有帮助的各种帖子,但并没有解决我的问题。

Posts, Documentation, Twitt : 帖子,文档,Twitt:

Missing dSYM , No matching UUID , Official Documentation but also It looks like we are missing dSYMs. 缺少dSYM没有匹配的UUID官方文档,但也好像我们缺少dSYM。

Here is my configuration and what I have tried so far : 这是我的配置以及到目前为止我已尝试的操作:

在此处输入图片说明

  • I have bitcode enabled (watchOS support) 我启用了位码(watchOS支持)
  • I have downloaded dSYM from iTunesConnect -> Without Success 我已经从iTunesConnect下载dSYM->没有成功
  • I searched in the archive from the Organizer (Show Package) -> Without Success 我从管理器(显示程序包)->没有成功的档案中搜索
  • I have set DWARF with dSYM file in the Build Settings. 我在“构建设置”中使用dSYM文件设置了DWARF。

I don't have matching UUID, like I read in some posts, it's because Apple compile the App again when you have bitcode enabled. 我没有匹配的UUID,就像我在某些帖子中读到的那样,这是因为在启用位码后,Apple会再次编译该应用程序。

What should I do now ? 我现在应该怎么办 ? We released a new version and now Crashlytics Dashboard is getting messy with all those missing dSYMs, for 2 different versions now. 我们发布了一个新版本,现在Crashlytics Dashboard对于所有缺少的dSYM都变得一团糟,现在有2个不同的版本。

If someone has additional information that I didn't read or know about, I am open-minded for suggestions. 如果某人有我未曾阅读或不了解的其他信息,那么我很乐意为您提供建议。

NB: I have bitcode enabled for my Watch and Watch extension target, and the whole project, but not for my main target nor the widget . 注意: 我为Watch和Watch扩展目标以及整个项目启用了位码,但没有为我的主要目标或widget启用了位码

Thanks for reaching out on this, Todd from Fabric. 谢谢您与我们联系,来自Fabric的Todd。

We do not currently support WatchOS crashes. 我们目前不支持WatchOS崩溃。 We tested heavily when watchOS 2 came out, but unfortunately there were many changes to the APIs in that version. 当watchOS 2推出时,我们进行了大量测试,但是不幸的是,该版本中的API进行了许多更改。 One of the changes heavily restricted our ability to capture information reliably and also get that information out. 更改之一严重限制了我们可靠地捕获信息以及将信息发布出去的能力。 Since we couldn't do this reliability without using private APIs, we don't have support for it. 由于不使用私有API就无法实现这种可靠性,因此我们对此不提供支持。

Thanks! 谢谢!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM