# Cocoa Error Monitoring

> Cocoa error monitoring captures crashes recorded on macOS, iOS, & tvOS, allowing you to get error details without digging through logs. Learn more here.

**URL:** https://sentry.io/for/cocoa/

---

Sentry automatically captures crashes recorded on macOS, iOS, and tvOS. See Cocoa error details like function, filename, and line number without ever digging through iOS crash logs.

**Documentation:** [https://docs.sentry.io/platforms/apple/](https://docs.sentry.io/platforms/apple/)

## Features

### Cocoa Performance Monitoring

Within minutes after installing Sentry, software teams are able to trace Cocoa performance issues back to a poor performing API call as well as surface all related code errors. Engineering Managers and Developers now have a single tool to optimize the performance of their code and deliver fast customer experiences with [Performance Monitoring](/for/performance/).

### Get iOS Crash Reporting With Complete Stack Traces

Reveal hidden context in Apple's incomplete crash data by automatically symbolicating unreadable symbols. Handle Cocoa iOS crashes with complete context using the React Native SDK while the Objective-C SDK runs in the background.

### Fill In The Blanks About iOS Crashes

See what the app was doing when the iOS crash occurred: every user action, controller changes, and custom breadcrumbs. Record events when devices are offline or in airplane mode, then send crash reports as soon as connection is regained.

### Resolve iOS Crashes With Better Data

Improve Cocoa error monitoring workflow with a full view of releases so you can mark errors as resolved and prioritize live issues. Learn in which version bug first appeared, merge duplicates, and know if things regress in a future release. Add commit data to automatically suggest an owner of each iOS crash and instantly send deploy emails.

## FAQ

**What is the difference between Sentry and traditional logging?**

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail [here](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/).

**What  languages does Sentry support?**

Sentry supports every major  language, framework, and library. You can browse each of them [here](/platforms/).

**How much does Sentry cost?**

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our [pricing page](/pricing/).

**How does Sentry impact the performance of my app?**

Sentry doesn't impact a web site's performance.

If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

---

*Source: [sentry.io/for/cocoa/](https://sentry.io/for/cocoa/)*