IOS 之CrashLog 错误日志

最新推荐文章于 2025-08-07 16:13:49 发布

Ittttttttta

最新推荐文章于 2025-08-07 16:13:49 发布

阅读量381

点赞数

分类专栏： StackOverFlow-IOS 文章标签： ios CrashLog

StackOverFlow-IOS 专栏收录该内容

34 篇文章

订阅专栏

本文提供了一套详细的步骤来分析从苹果应用商店推送的应用崩溃报告。包括如何复制崩溃报告所需的文件，使用终端命令进行内存地址定位，以及如何对IPA进行符号化处理。此外，文章还介绍了在不使用.dSYM文件的情况下进行IPA符号化的技巧。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Steps to analyze crash report from apple:

Copy the release .app file which was pushed to the appstore, the .dSYM file that was created at the time of release and the crash report receive from APPLE into a FOLDER.

OPEN terminal application and go to the folder created above (using cd command)

Run atos -arch armv7 -o APPNAME.app/APPNAME MEMORY_LOCATION_OF_CRASH. The memory location should be the one at which the app crashed as per the report.

Ex: atos -arch armv7 -o ‘APPNAME.app’/’APPNAME’ 0x0003b508

This would show you the exact line, method name which resulted in crash.

Ex: [classname functionName:]; -510

Symbolicating IPA

if we use IPA for symbolicating - just rename the extention .ipa with .zip , extract it then we can get a Payload Folder which contain app. In this case we don’t need .dSYM file.

Note

This can only work if the app binary does not have symbols stripped. By default release builds stripped the symbols. We can change it in project build settings “Strip Debug Symbols During Copy” to NO.
moreDetails
StackOverFlow