根据崩溃报告查找 iOS 崩溃的位置
Find where iOS is crashing based on crash reports
我有一个使用 TestFlight 的测试版应用程序，我注意到出现了崩溃报告。
大多数报告都是这样
如果我单击 Organizer 中的按钮 Open in project，它不会带我到任何地方
这似乎是内部崩溃，对吗？
如何找出导致崩溃的 UIBarButtonItem 原因？
我希望这会对您有所帮助：Apple doc Crash Report，正如您在 清单 4 的文档中看到的那样，崩溃报告是完全符号化的，清单 6 显示部分符号化的崩溃报告，看起来像您的情况
来自 Apple 文档
You must keep both the application binary and the .dSYM file in order to be able to fully symbolicate crash reports. You should archive these files for every build that you submit to iTunes Connect. The .dSYM and application binary are specifically tied together on a per-build-basis, and subsequent builds, even from the same source files, will not interoperate with files from other builds. If you use Xcode's Build and Archive command then they will be placed in a suitable location automatically. Otherwise any location searchable by Spotlight (such as your home directory) is fine.
有关此内容的更多信息，您可以查看 Symbolication
中 清单 6 之后的部分
您可以使用 crashlytics 来识别应用程序的位置 crashed.It 还会提供控制器名称和代码行号。
https://docs.fabric.io/ios/index.html Document
我有一个使用 TestFlight 的测试版应用程序，我注意到出现了崩溃报告。
大多数报告都是这样
如果我单击 Organizer 中的按钮 Open in project，它不会带我到任何地方
这似乎是内部崩溃，对吗？
如何找出导致崩溃的 UIBarButtonItem 原因？
我希望这会对您有所帮助：Apple doc Crash Report，正如您在 清单 4 的文档中看到的那样，崩溃报告是完全符号化的，清单 6 显示部分符号化的崩溃报告，看起来像您的情况
来自 Apple 文档
You must keep both the application binary and the .dSYM file in order to be able to fully symbolicate crash reports. You should archive these files for every build that you submit to iTunes Connect. The .dSYM and application binary are specifically tied together on a per-build-basis, and subsequent builds, even from the same source files, will not interoperate with files from other builds. If you use Xcode's Build and Archive command then they will be placed in a suitable location automatically. Otherwise any location searchable by Spotlight (such as your home directory) is fine.
有关此内容的更多信息，您可以查看 Symbolication
中 清单 6 之后的部分您可以使用 crashlytics 来识别应用程序的位置 crashed.It 还会提供控制器名称和代码行号。 https://docs.fabric.io/ios/index.html Document