简体   繁体   English

如果Crashlytics投诉我丢失的dSYM,它将跟踪用户的崩溃

[英]Will Crashlytics Track User Crashes if it is Complaining About my Missing dSYMs

Will Crashlytics Track User Crashes if it is Complaining About my Missing dSYMs? 如果Crashlytics对我丢失的dSYM提出投诉,是否会跟踪用户崩溃?

I believe my issue is that "$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)" for XCODE 10 might not know where to look since I have a dev and prod info.plist file, but Firebase Crashlytics website doesn't say much about this. 我认为我的问题是XCODE 10的“ $(BUILT_PRODUCTS_DIR)/ $(INFOPLIST_PATH)”可能不知道在哪里寻找,因为我有一个dev和prod info.plist文件,但是Firebase Crashlytics网站对此不多说。

If you don't upload the dSYMs, it will captures the crashes, but it doesn't include them in the standard reporting. 如果您不上传dSYM,它将捕获崩溃,但不会将它们包含在标准报告中。 But you can retroactively upload the missing dSYMs and the crash reports will suddenly become visible/usable. 但是,您可以追溯上载丢失的dSYM,并且崩溃报告将突然变为可见/可用。

For previous releases, you might check https://appstoreconnect.apple.com , as there's a link to download the dSYMs there, which you can then upload to Crashlytics. 对于以前的版本,您可以检查https://appstoreconnect.apple.com ,因为那里有一个链接来下载dSYM,然后可以将其上载到Crashlytics。 I'd suggest referring to the Crashlytics document titled Get deobfuscated crash reports for the process of making sure you get these dSYMs uploaded in the future. 建议您参考Crashlytics文档,标题为“ 获取反混淆的崩溃报告 ”,以确保将来获得这些dSYM。


Also see TN2151: Understanding and Analyzing Application Crash Reports for broader discussion of dSYMs. 另请参阅TN2151:了解和分析应用程序崩溃报告,以更广泛地讨论dSYM。 Also see WWDC 2018 video Understanding Crashes and Crash Logs . 另请参阅WWDC 2018视频了解崩溃和崩溃日志

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

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