Skip to content

reorder sections in apple usage so simplest thing is above the fold #13883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 4, 2025
Merged

reorder sections in apple usage so simplest thing is above the fold #13883

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2f56f4
reorder sections in apple usage so simplest thing is above the fold
armcknight May 29, 2025
74d2b2c
Apply suggestions from code review
armcknight Jun 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/platforms/apple/common/usage/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,18 @@ Key terms:

</Alert>

The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
## Capturing Messages

While capturing an event, you can also record the breadcrumbs that lead up to that event. Breadcrumbs are different from events: they will not create an event in Sentry, but will be buffered until the next event is sent. Learn more about breadcrumbs in our <PlatformLink to="/enriching-events/breadcrumbs/">Breadcrumbs documentation</PlatformLink>.
The simplest operation is to capture a bare message: textual information that should be sent to Sentry. Typically, our SDKs won't automatically capture messages, but you can capture them manually.

## Capturing Errors
Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-error" />
<PlatformContent includePath="capture-message" />

## Capturing Messages
## Capturing Errors

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.
The most common usage of the Apple SDKs is to capture errors. In general, if you have something that looks like an exception, it can be captured, though this varies by platform. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. This is also useful for manual reporting of errors or messages to Sentry.

Messages show up as issues on your issue stream, with the message as the issue name.
While capturing an event, you can also record the breadcrumbs that lead up to that event. Breadcrumbs are different from events: they will not create an event in Sentry, but will be buffered until the next event is sent. Learn more in our <PlatformLink to="/enriching-events/breadcrumbs/">Breadcrumbs documentation</PlatformLink>.

<PlatformContent includePath="capture-message" />
<PlatformContent includePath="capture-error" />