Features
Here's a list of Sentry's Apple SDK features.
Sentry's Apple SDK enables automatic reporting of errors and exceptions, and identifies performance issues in your application.
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.
All features listed below are enabled by default unless otherwise noted. Some features have platform-specific limitations or version requirements, which are indicated where applicable.
- Multiple types of errors are captured, including:
- Mach exceptions
- Fatal signals
- Unhandled exceptions
- C++ exceptions
- Objective-C exceptions
- Error messages of
fatalError,assert, andprecondition - 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.
- App Hang Detection
- On iOS and tvOS: Differentiates between fully-blocking and non-fully-blocking app hangs, and measures app hang duration (AppHangsV2, enabled by default since SDK version 9.0.0)
- Watchdog Terminations (only available on iOS, tvOS, and visionOS)
- HTTP Client Errors
- Automatic Performance Tracking for:
- Rendering of UIViewControllers
- Performance of HTTP requests
- Distributed tracing
- Insights for Mobile Vitals
- Cold and warm start
- Slow and frozen frames
- Prewarmed App Start Tracing
- Performance of File I/O operations
- Performance of Core Data queries
- User Interaction transactions for UI clicks
- Frame rate tracking for UI performance (only available on iOS, tvOS, and visionOS)
- App start time measurement for cold and warm starts (only available on iOS, tvOS, and visionOS)
- Profiling (requires configuration, only available on iOS and macOS)
- Transaction-based profiling (deprecated)
- Continuous profiling
- UI Profiling (recommended)
- Launch profiling
- Swift Async/Await support for stitching together stack traces of Swift concurrency code
- Release health tracks crash-free users and sessions
- Session tracking automatically tracks user sessions for release health metrics
- Session Replay (only available on iOS 16+ and tvOS 16+)
- Requires SDK version 8.31.1 or later
- tvOS is not officially supported
- Events enriched with device data, environment information, and app state
- Breadcrumbs are automatically captured for:
- Application lifecycle events (
didBecomeActive,didEnterBackground,viewDidAppear) - Touch events
- System events (battery level or state changed, memory warnings, device orientation changed, keyboard did show and did hide, screenshot taken, time zone changed or significant time change)
- Outgoing HTTP requests
- Application lifecycle events (
- Attachments enrich your event by storing additional files, such as config or log files
- Source Context shows snippets of code around the location of stack frames
- View Hierarchy and Screenshot attachments for errors (only available on iOS and tvOS)
- User Feedback provides the ability to collect user information when an event occurs (User Feedback UI only available on iOS 13+)
- MetricKit integration (only available on iOS 15+ and macOS 12+, requires enabling
enableMetricKitoption) - Logs capturing (requires
enableLogsoption, only available on iOS, tvOS, visionOS, and macOS)
- Offline caching when a device is unable to connect; we send a report once we receive another event
- Event persistence: crash reports persist to disk and are sent upon application start if not sent immediately after a crash
For information about experimental features, see the Experimental Features page.
For platform-specific feature details and limitations, see:
Was this helpful?
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").