docs(apple): Document enableMemoryIntrospection option - #18838
#18838Open
NinjaLikesCheez wants to merge 2 commits into
mastergetsentry/sentry-docs:masterfrom
docs/apple-memory-introspection-optiongetsentry/sentry-docs:docs/apple-memory-introspection-optionCopy head branch name to clipboard
Open
docs(apple): Document enableMemoryIntrospection option#18838NinjaLikesCheez wants to merge 2 commits intomastergetsentry/sentry-docs:masterfrom docs/apple-memory-introspection-optiongetsentry/sentry-docs:docs/apple-memory-introspection-optionCopy head branch name to clipboard
NinjaLikesCheez wants to merge 2 commits into
mastergetsentry/sentry-docs:masterfrom
docs/apple-memory-introspection-optiongetsentry/sentry-docs:docs/apple-memory-introspection-optionCopy head branch name to clipboard
Conversation
Add documentation for the new enableMemoryIntrospection option that allows users to control whether memory introspection data is included in crash reports. This option helps users manage sensitive data by allowing them to disable stack contents capture near crash sites. - Add enableMemoryIntrospection option to configuration options - Update sensitive data documentation to mention memory introspection - Link between the two documentation sections for better discoverability Ref: getsentry/sentry-cocoa#8571
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
9 tasks
philipphofmann
approved these changes
Jul 27, 2026
philipphofmann
left a comment
Member
There was a problem hiding this comment.
LGTM, after clarifying if this is really enabled by default?
|
|
||
| </SdkOption> | ||
|
|
||
| <SdkOption name="enableMemoryIntrospection" type="bool" defaultValue="true" availableSince="9.24.0"> |
Member
There was a problem hiding this comment.
h: Wait, is the default really true? If it contains sensitive information, the default should be false.
Member
Author
There was a problem hiding this comment.
Adding a link to the decision to change it: getsentry/sentry-cocoa#8571 (comment)
Member
Author
There was a problem hiding this comment.
Addressed the docs comment in dfeb7b5. Please resolve the thread if you're happy with the fix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Add documentation for the new
enableMemoryIntrospectionoption that allows users to control whether memory introspection data is included in crash reports. This option helps users manage sensitive data by allowing them to disable stack contents capture near crash sites.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
ref: getsentry/sentry-cocoa#8571