From b816e75d752744f881f4dc1e0d079434243321e5 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Thu, 10 Apr 2025 16:47:28 +0200 Subject: [PATCH 1/2] fix(apple): Not taking screenshots for all crashes Explain why the Cocoa SDK can't capture screenshots for all types of crashes. --- .../apple/common/enriching-events/screenshots/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx index eb07022c2ccda0..f9d014ceef7fb9 100644 --- a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx +++ b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx @@ -10,7 +10,7 @@ notSupported: - apple.watchos --- -Sentry makes it possible to automatically take a screenshot and include it as an attachment when a user experiences an error, an exception or a crash. +Sentry makes it possible to automatically take a screenshot and include it as an attachment when a user experiences an error, an exception or a crash. When a crash occurs on Apple operating systems, there is no guarantee that the Cocoa SDK can still capture a screenshot because, strictly speaking, you're not allowed to call any async unsafe code. Still, it works in most cases, but we can't guarantee screenshots for all types of crashes. This feature is only available for SDKs with a user interface, like the ones for mobile and desktop applications. It's also limited by whether taking a screenshot is possible or not. For example, in some environments, like native iOS, taking a screenshot requires the UI thread, which often isn't available in the event of a crash. Another example where a screenshot might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution. From 85cea1a2ee27b82d7235a400a032195a639c1415 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Tue, 15 Apr 2025 15:37:50 +0200 Subject: [PATCH 2/2] Update docs/platforms/apple/common/enriching-events/screenshots/index.mdx Co-authored-by: Alex Krawiec --- .../apple/common/enriching-events/screenshots/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx index f9d014ceef7fb9..e1c710748c085f 100644 --- a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx +++ b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx @@ -10,7 +10,7 @@ notSupported: - apple.watchos --- -Sentry makes it possible to automatically take a screenshot and include it as an attachment when a user experiences an error, an exception or a crash. When a crash occurs on Apple operating systems, there is no guarantee that the Cocoa SDK can still capture a screenshot because, strictly speaking, you're not allowed to call any async unsafe code. Still, it works in most cases, but we can't guarantee screenshots for all types of crashes. +Sentry makes it possible to automatically take a screenshot and include it as an attachment when a user experiences an error, an exception or a crash. When a crash occurs on Apple operating systems, there is no guarantee that the Cocoa SDK can still capture a screenshot since you're technically not allowed to call any async unsafe code. While it still works in most cases, we can't guarantee screenshots for all types of crashes. This feature is only available for SDKs with a user interface, like the ones for mobile and desktop applications. It's also limited by whether taking a screenshot is possible or not. For example, in some environments, like native iOS, taking a screenshot requires the UI thread, which often isn't available in the event of a crash. Another example where a screenshot might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.