Skip to content

Commit aaed0e7

Browse files
Apply suggestions from code review
Co-authored-by: Philipp Hofmann <[email protected]>
1 parent 48c12d2 commit aaed0e7

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

docs/platforms/apple/guides/ios/session-replay/customredact.mdx

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ description: "Learn how to mask parts of your app's data in Session Replay."
66
---
77

88
<Alert>
9+
Before publising an App with Session Replay enabled, make sure to test it thoroughly to ensure that no sensitive data is exposed.
910

1011
If you choose to use custom masking in your Session Replays, you may accidentally expose sensitive customer data. Be sure to double-check what you choose to expose.
1112

@@ -16,9 +17,9 @@ By default, our Session Replay SDK masks all text content, images, and user inpu
1617

1718
## Mask by View Class
1819

19-
You can choose which type of view you want to mask or ignore by using the `maskedViewClasses` or `unmaskedViewClasses` options.
20+
You can choose which type of view you want to mask or unmask by using the `maskedViewClasses` or `unmaskedViewClasses` options.
2021

21-
Let's say you have a custom view that you want to mask and a `UILabel` subclass (which normally would be masked) that you doesn't want to mask. You can set the options like this:
22+
Let's say you have a custom view that you want to mask and a `UILabel` subclass (which normally would be masked) that you don't want to mask. You can set the options like this:
2223

2324
```swift
2425
options.experimental.sessionReplay.maskedViewClasses = [MyCustomView.self]
@@ -74,9 +75,3 @@ To hide the username, we need to mask it.
7475
.sentryReplayUnmask()
7576
}
7677
```
77-
78-
<Alert>
79-
80-
Before publising an App with Session Replay enabled, make sure to test it thoroughly to ensure that no sensitive data is exposed.
81-
82-
</Alert>

0 commit comments

Comments
 (0)