对崩溃日志进行符号化的最简单方法:

在IPA构建过程中保存组织者的xcarchive文件，以备将来使用。 当崩溃发生时，从受影响的设备上收集崩溃日志。扩展名应该是.crash。如果崩溃日志是.ips格式，只需将其重命名为.crash。 双击存储路径中的xcarchive，使其出现在管理器中(如果尚未出现)。 打开xcode窗口->设备和模拟器->查看设备日志->所有日志->拖放.crash文件。

等待5秒。砰!堆栈跟踪中的应用程序调用将被符号化! 不过，你仍然可以看到很多符号!这些是内部库和框架调用。

这是最简单的一种方法，我已经试过了!

我努力有崩溃报告符号化通过atos，但我不愿意，因为这个过程似乎很麻烦，但我发现崩溃报告在Xcode->窗口->组织者->崩溃(在左侧菜单)Xcode会自动下载崩溃日志，并将自动符号化，从那里你可以很容易地找到崩溃的原因。

苹果公司的文件如下:

符号崩溃报告与Xcode Xcode会自动尝试符号化它遇到的所有崩溃报告。你所需要做的就是将崩溃报告添加到Xcode管理器中。

Connect an iOS device to your Mac Choose "Devices" from the "Window" menu Under the "DEVICES" section in the left column, choose a device Click the "View Device Logs" button under the "Device Information" section on the right hand panel Drag your crash report onto the left column of the presented panel Xcode will automatically symbolicate the crash report and display the results To symbolicate a crash report, Xcode needs to be able to locate the following: The crashing application's binary and dSYM file. The binaries and dSYM files for all custom frameworks that the application links against. For frameworks that were built from source with the application, their dSYM files are copied into the archive alongside the application's dSYM file. For frameworks that were built by a third-party, you will need to ask the author for the dSYM file. Symbols for the OS that the that application was running on when it crashed. These symbols contain debug information for the frameworks included in a specific OS release (e.g, iOS 9.3.3). OS symbols are architecture specific - a release of iOS for 64-bit devices won't include armv7 symbols. Xcode will automatically copy OS symbols from each device that you connect to your Mac.

如果其中任何一个缺失，Xcode可能无法代表这个崩溃报告，或者只能部分代表这个崩溃报告。

您需要访问包含DWARF文件的. dsym包(文件夹)，并且应该使用编辑器打开.crash文件。

查看回溯部分，你应该会看到如下内容:

...
13  TheElements                         0x0000000100f62ca0 0x100f5c000 + 27808
14  UIKitCore                       0x00000001843e3044 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 356 (UIApplication.m:2328)
...

Binary Images:
0x100f5c000 - 0x101673fff TheElements arm64 ...
...

注意stacktrace部分的第3列(0x0000000100f62ca0)中的长地址。 注意第4列中的简短地址(0x100f5c000) 注意二进制图像部分的架构(arm64) 执行以下操作:

$ atos -arch <arch> -o TheElements.app.dSYM/Contents/Resources/DWARF/TheElements -l <short_address> <long_address>

你应该得到这样的结果:

-[AtomicElementViewController myTransitionDidStop:finished:context:]

权威来源:https://developer.apple.com/library/content/technotes/tn2151/_index.html#//apple_ref/doc/uid/DTS40008184-CH1-SYMBOLICATE_WITH_ATOS

注意:如果由于任何原因你无法访问. dsym文件，你可以使用Xcode>Product>Archive重新创建.xcarchive，但要确保你构建的是完全相同的代码。然后可以从.xcarchive包中提取符号。

使用Xcode有一个更简单的方法(不需要使用命令行工具，一次查找一个地址)

Take any .xcarchive file. If you have one from before you can use that. If you don't have one, create one by running the Product > Archive from Xcode. Right click on the .xcarchive file and select 'Show Package Contents' Copy the dsym file (of the version of the app that crashed) to the dSYMs folder Copy the .app file (of the version of the app that crashed) to the Products > Applications folder Edit the Info.plist and edit the CFBundleShortVersionString and CFBundleVersion under the ApplicationProperties dictionary. This will help you identify the archive later Double click the .xcarchive to import it to Xcode. It should open Organizer. Go back to the crash log (in Devices window in Xcode) Drag your .crash file there (if not already present) The entire crash log should now be symbolicated. If not, then right click and select 'Re-symbolicate crash log'

对我来说，.crash文件就足够了。没有。dsym文件和。app文件。

我在mac上运行了这两个命令，在那里我建立了存档，它工作了:

export DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer" 

/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash  /yourPath/crash1.crash > /yourPath/crash1_symbolicated.crash