Ingest os_activity tracing

[lhunath]

Problem Statement

Apple has support for some advanced tooling to keep track of the origin of a crash beyond what backtraces can provide, in their OS framework's activity tracing. This allows applications to declare what activity is in progress, attaching breadcrumbs and context, which is subsequently included in crash reports, even if the crash happened on a distant thread with the original context of the crash absent from the backtrace.

Solution Brainstorm

I am curious if Sentry is capable of ingesting this information and attaching it to crash logs.

More details can be found:

• https://developer.apple.com/documentation/os/collecting-log-messages-in-activities
• https://www.objc.io/issues/19-debugging/activity-tracing/
• https://developer.apple.com/documentation/swiftui/view/interactionactivitytrackingtag(_:)

Are you willing to submit a PR?

No response

[brustolin]

Hello @lhunath, thanks for the suggestion. We will investigate it.