Skip to content

Commit 2172335

Browse files
authored
Add masking options to AndroidManifest
1 parent 8e4c9a3 commit 2172335

File tree

1 file changed

+7
-2
lines changed
  • docs/platforms/android/session-replay

1 file changed

+7
-2
lines changed

docs/platforms/android/session-replay/index.mdx

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,8 @@ SentryAndroid.init(context) { options ->
6969
```
7070

7171
```XML {filename:AndroidManifest.xml}
72-
<meta-data android:name="io.sentry.session-replay.on-error-sample-rate" android:value="1.0" />
73-
<meta-data android:name="io.sentry.session-replay.session-sample-rate" android:value="1.0" />
72+
<meta-data android:name="io.sentry.session-replay.on-error-sample-rate" android:value="1.0" />
73+
<meta-data android:name="io.sentry.session-replay.session-sample-rate" android:value="1.0" />
7474
```
7575

7676
## Verify
@@ -113,6 +113,11 @@ options.experimental.sessionReplay.maskAllImages = false
113113
// options.experimental.sessionReplay.redactAllImages = false
114114
```
115115

116+
```XML {filename:AndroidManifest.xml}
117+
<meta-data android:name="io.sentry.session-replay.mask-all-text" android:value="false" />
118+
<meta-data android:name="io.sentry.session-replay.mask-all-images" android:value="false" />
119+
```
120+
116121
## Error Linking
117122

118123
Errors that happen while a replay is running will be linked to the replay, making it possible to jump between related issues and replays. However, it's **possible** that in some cases the error count reported on the **Replays Details** page won't match the actual errors that have been captured. That's because errors can be lost, and while this is uncommon, there are a few reasons why it could happen:

0 commit comments

Comments
 (0)