Excerpt
Incident Identifier: A unique identifier for the report. Two reports will never share the same Incident Identifier.
CrashReporter Key: An anonymized per-device identifier. Two reports from the same device will contain identical values.
Beta Identifier: A unique identifier for the combination of the device and vendor of the crashed application. Two reports for applications from the same vendor and from the same device will contain identical values. This field is only present in crash reports generated for applications distributed through TestFlight, and replaces the CrashReporter Key field.
Process: The executable name for the process that crashed. This matches the value for the CFBundleExecutable key in the application's information property list.
Version: The version of the process that crashed. The value for this field is a concatenation of the crashed application's CFBundleVersion and CFBundleVersionString.
Code Type: The target architecture of the process that crashed. This will be one of ARM-64, ARM, x86-64, or x86.
Role: The task_role assigned to the process at the time of termination.
OS Version: The OS version, including the build number, on which the crash occurred.
Exception Codes: Processor specific information about the exception encoded into one or more 64-bit hexadecimal numbers. Typically, this field will not be present because the Crash Reporter parses the exception codes to present them as a human-readable description in the other fields.
Exception Subtype: The human-readable name of the exception codes.
Exception Message: Additional human-readable information extracted from the exception codes.
Exception Note: Additional information that is not specific to one exception type. If this field contains SIMULATED (this is NOT a crash) then the process did not crash, but was killed at the request of the system, typically the watchdog.
Termination Reason: Exit reason information specified when a process is terminated. Key system components, both inside and outside of a process, will terminate the process upon encountering a fatal error (e.g. a bad code signature, a missing dependent library, or accessing privacy sensitive information without the proper entitlement). macOS Sierra, iOS 10, watchOS 3, and tvOS 10 have adopted new infrastructure to record these errors, and crash reports generated by these operating systems list the error messages in the Termination Reason field.
Triggered by Thread: The thread on which the exception originated
Application Specific Information: framework error messages captured just before the process terminated
Kernel Messages: details about code-signature problems
Dyld Error Messages: error messages emitted by the dynamic linker
