From d6d0f330bff035d656a3df81f441902d32478030 Mon Sep 17 00:00:00 2001 From: rodolfoBee <64906376+rodolfoBee@users.noreply.github.com> Date: Mon, 2 Dec 2024 14:39:27 +0100 Subject: [PATCH] Remove attach_stacktrace This options is not present in the SDK --- docs/platforms/native/common/configuration/options.mdx | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/platforms/native/common/configuration/options.mdx b/docs/platforms/native/common/configuration/options.mdx index 83ccc15db16f7..59d51c4e1e900 100644 --- a/docs/platforms/native/common/configuration/options.mdx +++ b/docs/platforms/native/common/configuration/options.mdx @@ -63,16 +63,6 @@ This variable controls the total amount of breadcrumbs that should be captured. - - -When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option, for instance, means that stack traces appear next to all log messages. - -This option is turned off by default. - -Grouping in Sentry is different for events with stack traces and without. As a result, you will get new groups as you enable or disable this flag for certain events. - - - ## Hooks These options can be used to hook the SDK in various ways to customize the reporting of events.