Support ingesting Apple JSON .ips crash report format

Support ingesting Apple's JSON .ips crash report format as an alternative input to the Sentry Apple SDK. This would allow teams to bring externally-collected crash reports into Sentry without requiring SDK instrumentation at crash time.

Current behavior

The Sentry Apple SDK captures crashes at runtime and encodes them in Sentry's own envelope format. There is no way to ingest pre-existing .ips crash reports generated by the OS.

Gap

Apple has documented a stable JSON crash report format (.ips) since macOS 12 / iOS 15 (Apple developer docs). Crash reports in this format are produced by:

• macOS / iOS crash reporter (written to disk at crash time)
• Xcode Organizer
• TestFlight
• App Store Connect

Teams that collect these reports outside of the Sentry SDK pipeline have no way to ingest them into Sentry today. This creates a gap for scenarios such as:

• Crashes that occur before the SDK initializes
• Reports collected from devices that don't run Sentry-instrumented builds
• Post-hoc analysis of OS-generated crash logs

Options

• A sentry-cli command or API endpoint that accepts .ips files, parses them, and submits corresponding Sentry events, related issue: https://github.com/getsentry/sentry-cli/issues/2663
• Backend-only ingestion endpoint that accepts raw .ips JSON payloads directly

Start by comparing the two proposed entry points: a sentry-cli command or API endpoint accepting raw Apple .ips JSON. Determine which ingestion path is intended, then define parsing and event-submission behavior; the work is done when externally collected reports can be ingested into Sentry without SDK instrumentation.