You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add capture(error:attachAllThreads:block:) combined API to SentrySDK #8538
When capturing errors where full thread stack traces are needed for specific events only (rather than globally via SentryOptions.attachAllThreads), there is currently no clean way to also mutate the scope for that same call. The only workarounds are:
Enabling attachAllThreads globally at init, which may not be desirable for performance reasons.
Using configureScope before the capture call, which sets data globally and requires manual cleanup.
Expected behaviour:
The method would behave identically to the existing capture(error:block:) variant (cloning the current scope and applying mutations only to the captured event) while also forwarding the attachAllThreads flag to the underlying client.
Activity
linear-code commentedon Jul 23, 2026
COCOA-1710
sergiisukhanov commentedon Jul 23, 2026
Thanks a lot @masinette for raising an issue. 🙏
I would like to add: this relates to all four
.capture(options (not.capture(error: Error, ...)only):.capture(error: Error, ...).capture(event: Event, ...).capture(message: String, ...).capture(exception: exception, ...)It would be great to have these four public methods 😃
sergiisukhanov commentedon Jul 23, 2026
In addition: it would be really great to have this change as 9.14.1: on top of 9.14.0 release (since 9.14.0 is the latest stable release).