Skip to main content

macOS crash reporting

Your Mac app crashed on a machine you'll never see. Fix it anyway.

BugSplat captures the crash from your macOS app, symbolicates it against your dSYMs, and shows you the faulting line, without waiting for a user to email you a crash log.

Why BugSplat for macOS

Mac crashes report themselves and symbolicate against your dSYMs, so Swift, Objective-C, and C++ frames read with file and line.

01 · It lands

Something breaks in your macOS build. You find out first.

BugSplat captures crashes from native macOS apps automatically, whether Swift, Objective-C, or C++ under the hood. Crash report, thread state, OS version, and hardware details land in the same dashboard as every other platform you ship.

  • Crashes captured automatically from shipped Mac apps
  • Symbolicated against the dSYMs from the exact build
  • Apple silicon and Intel Macs in one dashboard
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how macOS crashes arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups macOS crashes your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Stacks symbolicate against your uploaded dSYMs, so you see readable Swift and Objective-C frames with file and line numbers.

  • Thousands of reports collapse into a short list of distinct bugs
  • Function names and line numbers, not memory addresses
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerts for macOS crashes reach Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

Crash reporting built for native code.

The part of macOS crash reporting that's hard is the part we've always done.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a macOS question and you'll hear back from an engineer who builds BugSplat, usually the same day.

macOS setup

Wire up macOS and read a real stack the same day.

Add the SDK and upload symbols with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .