简体   繁体   English

iOS 应用程序具有神秘的 UUID,没有匹配的 dSYM,因此无法进行符号化

[英]iOS app has mysterious UUID with no matching dSYM so cannot symbolicate

I'm pretty familiar with how crash logs for iOS apps are symbolicated but this one is a head scratcher.我非常熟悉 iOS 应用程序的崩溃日志是如何符号化的,但这是一个令人头疼的问题。

I have MyApp with build 2345 that was released as a beta through TestFlight, using the normal Archive then Upload to App Store flow in Xcode 7.2 (7C68).我有构建 2345 的 MyApp,它通过 TestFlight 作为测试版发布,使用普通的存档然后上传到 Xcode 7.2 (7C68) 中的 App Store 流程。

When I do a dwarfdump for the binary in the the xcarchive, I get the following:当我对 xcarchive 中的二进制文件执行 dwarfdump 时,我得到以下信息:

dwarfdump --uuid MyApp.app/MyApp
UUID: 0BDA6D6F-3C0D-339E-842F-C2CB04199E10 (armv7) MyApp.app/MyApp
UUID: B2A69BEC-DF5E-33EA-A9E0-490EBF03074C (arm64) MyApp.app/MyApp

Here is the dwarfdump for the dSYM file:这是 dSYM 文件的 dwarfdump:

dwarfdump --uuid MyApp.app.dSYM
UUID: 0BDA6D6F-3C0D-339E-842F-C2CB04199E10 (armv7) MyApp.app.dSYM/Contents/Resources/DWARF/MyApp
UUID: B2A69BEC-DF5E-33EA-A9E0-490EBF03074C (arm64) MyApp.app.dSYM/Contents/Resources/DWARF/MyApp

So far, so good.到现在为止还挺好。

However, I received a crash through Organize > Crashes for build 2345 that has a different UUID for the binary:但是,我通过 Organize > Crashes for build 2345 收到了崩溃,它具有不同的二进制 UUID:

0x100054000 - 0x1000fffff myapp arm64  <3715db2438743cf5aac1742d9a214c2c> /var/mobile/Containers/Bundle/Application/7313BC02-3F90-4F94-82E2-CBDC941E5D68/MyApp.app/myapp
0x100144000 - 0x1001e7fff AWSCore arm64  <c2aa13236d0437b98194c0487db69e68> /var/mobile/Containers/Bundle/Application/7313BC02-3F90-4F94-82E2-CBDC941E5D68/blink.app/Frameworks/AWSCore.framework/AWSCore
....

I know for sure that the crash report is for the same build, yet the UUID here is 3715db2... when I am expecting it to be b2a69bec...我确定崩溃报告是针对同一个版本的,但这里的 UUID 是3715db2...当我期望它是b2a69bec...

I do have bitcode enabled so I tried doing a Download dSYMs from the Organizer Archive page (even though I built arm64 so Apple shouldn't have had to) and it retrieved dSYMs for the other UUIDs/binaries in the crash report but nothing for the myapp binary.我确实启用了位码,因此我尝试从 Organizer Archive 页面下载 dSYM(即使我构建了 arm64,因此 Apple 不必这样做)并且它为崩溃报告中的其他 UUID/二进制文件检索了 dSYM,但没有为myapp二进制文件。 In fact, the myapp binary is the only binary that didn't get a corresponding dSYM downloaded!事实上, myapp二进制文件是唯一没有下载相应 dSYM 的二进制文件!

So a couple questions:所以有几个问题:

  1. Where did the 3715db2438743cf5aac1742d9a214c2c version of the myapp binary come from? myapp 二进制文件的3715db2438743cf5aac1742d9a214c2c版本从何而来?
  2. How can I get the dSYM for it so that I can symbolicate the crash?我怎样才能获得它的 dSYM 以便我可以象征崩溃? Apple is not returning it with the "Download dSYMs" option in Xcode. Apple 不会通过 Xcode 中的“下载 dSYM”选项返回它。

Looks like I found the solution.看起来我找到了解决方案。

It's possible in case you set Bitcode enabled.如果您将 Bi​​tcode 设置为启用,则有可能。 To get necessary dSym you should either use "Download dSYMs..." button (Xcode / Organizer / Your Archive - right panel with archive information) or download them from iTunes Connect (Activity tab, link in build's details ).要获得必要的 dSym,您应该使用“下载 dSYM...”按钮(Xcode / Organizer / Your Archive - 带有存档信息的右侧面板)或从 iTunes Connect(活动选项卡,构建详细信息中的链接)下载它们。

iTunes 连接

Last option helped in my situation.最后一个选项对我的情况有所帮助。

  1. dSYM stored inside your .xcarchive Right click on archive in organiser then show package content. dSYM 存储在您的 .xcarchive 中右键单击管理器中的存档,然后显示包内容。 It should be there.它应该在那里。

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

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