From 0ca7599cf73b30d64dab0ed1775b8cef47a7a020 Mon Sep 17 00:00:00 2001
From: Antonis Lilis <antonis.lilis@sentry.io>
Date: Fri, 4 Sep 2026 10:52:58 +0200
Subject: [PATCH] feat(react-native): Document enableMemoryIntrospection iOS
 option

Adds the enableMemoryIntrospection option to the React Native
configuration reference. It lets apps omit crash-site memory contents
from native iOS crash reports.

Ref getsentry/sentry-react-native#6547
---
 .../react-native/common/configuration/options.mdx      | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/platforms/react-native/common/configuration/options.mdx b/docs/platforms/react-native/common/configuration/options.mdx
index 8d740ce518bc5..4910d79002794 100644
--- a/docs/platforms/react-native/common/configuration/options.mdx
+++ b/docs/platforms/react-native/common/configuration/options.mdx
@@ -452,6 +452,16 @@ Learn more in the <PlatformLink to="/configuration/metric-kit/">MetricKit</Platf
 
 </SdkOption>
 
+<SdkOption name="enableMemoryIntrospection" type="boolean" defaultValue="false" availableSince="8.26.0">
+
+When enabled, `SentryCrash` reads memory near the crash site while capturing a native crash on iOS (for example, `EXC_BAD_ACCESS`) and embeds string-based stack contents in the event under `exception.value`. This can help with debugging, but may also expose sensitive information (such as user IDs or personal data), which can even surface in the issue title.
+
+Set this boolean to `true` to include memory introspection data, or leave it disabled to keep native crash reporting while omitting memory contents. This option has no effect on Android.
+
+Learn more about managing sensitive data in the <PlatformLink to="/data-management/sensitive-data/">Scrubbing Sensitive Data</PlatformLink> documentation.
+
+</SdkOption>
+
 <SdkOption name="onReady" type="function">
 
 Set this callback, which is called after the Sentry React Native SDK initializes its Native SDKs (Android and iOS).