From 30808b4cf0c5843f482580582903bb315ffb167d Mon Sep 17 00:00:00 2001 From: J-P Nurmi Date: Wed, 13 May 2026 18:14:25 +0200 Subject: [PATCH] docs(native): Remove stale Crashpad attachment warning Remove the outdated macOS Crashpad limitation now that dynamic runtime attachments are supported. Co-Authored-By: OpenAI Codex --- platform-includes/enriching-events/add-attachment/native.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/platform-includes/enriching-events/add-attachment/native.mdx b/platform-includes/enriching-events/add-attachment/native.mdx index 200c8dd835397..bc58a16a98b80 100644 --- a/platform-includes/enriching-events/add-attachment/native.mdx +++ b/platform-includes/enriching-events/add-attachment/native.mdx @@ -43,8 +43,6 @@ sentry_capture_event_with_scope(event, scope); When using the `crashpad` backend, it writes byte attachments to disk into a flat directory structure. If multiple buffers are attached with the same `filename`, it will internally ensure unique filenames for attachments by appending a unique suffix to the filename. Therefore, attachments may show up with altered names in Sentry. -When using the `crashpad` backend on macOS, the list of attachments that will be added at the time of a hard crash will be frozen at the time of `sentry_init`, and later modifications will not be reflected. - ### Removing Scoped Attachments To remove attachments from the global scope, you can use the `sentry_attachment_t` handle returned by `sentry_attach_file`. After removing the attachment, the file will no longer be uploaded with any future events or crashes and the handle becomes invalid.