Features
Learn about Sentry's Apple SDK features for macOS.
Sentry's Apple SDK for macOS enables automatic reporting of errors and exceptions, and identifies performance issues in your application. The minimum supported macOS version is 10.10. The below, is a list of features that are available as part of this SDK.
For macOS, a simple manual setup is required for the SDK to report uncaught exceptions.
The SDK builds a crash report that persists to disk. While it attempts to send the report right after the crash, it may not always work because the environment may be unstable at the time of the crash. If this is the case, the report will be sent upon application start.
Features:
- Multiple types of errors are captured, including:
- Mach exceptions
- Fatal signals
- Unhandled exceptions
- C++ exceptions
- Objective-C exceptions
- Error messages of fatalError, assert, and precondition
- Start-up crashes. The SDK init waits synchronously for up to 5 seconds to flush out events if the app crashes within 2 seconds after the SDK init.
- Events enriched with device data
- Offline caching when a device is unable to connect; we send a report once we receive another event
- Breadcrumbs automatically captured for
- Application lifecycle events (
didBecomeActive,didEnterBackground) - Touch events
- System events (battery level or state changed, memory warnings, device orientation changed, keyboard did show and did hide, screenshot taken)
- Outgoing HTTP requests
- Application lifecycle events (
- Release health tracks crash free users and sessions
- Attachments enrich your event by storing additional files, such as config or log files
- User Feedback provides the ability to collect user information when an event occurs
- Source Context shows snippets of code around the location of stack frames
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").