-1

"Crash log analysis for iOS15 and later" describes how to analyze crash logs using CrashSymbolicator.py instead of symbolicatecrash.

If we have a .ips file, it seems that we can symbolize the crash log with a command like the one below.

python3 /Applications/Xcode.app/Contents/SharedFrameworks/CoreSymbolicationDT.framework/Resources/CrashSymbolicator.py -p foo.ips -d Foo.app.dSYM -o piyo.ips

But I don't know how to find the .ips file. In order to analyze the user's crash log from the XCode Organizer, right-click on "Crashes" and click "Show in Finder" to display a group of files "xxxxx.crashpoint". If you right click on "xxxxx.crashpoint" and click "show package contents", you will find a folder called "Logs" in the folder called "Filters", and you will find a group of files called "xxxxx.crash" there.

I could only find .crash files. However, when I try to symbolize the .crash file with CrashSymbolicator.py as below, I get an error.

python3 /Applications/Xcode.app/Contents/SharedFrameworks/CoreSymbolicationDT.framework/Resources/CrashSymbolicator.py -p foo.crash -d Foo.app.dSYM -o piyo.crash

The error contents are as follows.

Crash log is missing bug_type field. Stopping symbolication.

Even using symbolicatecrash will result in an error, like this:

export DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer"
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash -d Foo.app.dSYM -o piyo.txt foo.crash

The error contents are as follows.

No symbolic information found

How can I symbolize the .crash file correctly?

HangarRash
  • 7,314
  • 5
  • 5
  • 32
gncc
  • 300
  • 4
  • 13
  • 1
    Why not open the .crash file with Xcode? It will ask what project to use and then it will show you a symbolicated stack trace and take you to the most relevant line of code in your project. No need for command line tools. – HangarRash Aug 24 '23 at 01:06

0 Answers0