You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3b6fa83
Browse filesBrowse the repository at this point in the historyBrowse files
feat(replay): Add pauseTouchTracking and resumeTouchTracking (#6546)
Apps can stop recording touches on sensitive screens, such as a custom PIN pad, while
the masked screen recording continues. Masking hides the content, but recorded touch
positions could reveal the input.
The flag is independent of pause()/resume() and is cleared only by
resumeTouchTracking(), also across new replays. It is set directly instead of being queued
on the main thread, so it applies to touch events that are already pending.
Also mark debugMaskingEnabled as volatile, it is written and read on different threads.
Fixes JAVA-658
Fixes#5787
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,10 @@
7
7
8
8
## Unreleased
9
9
10
+
### Features
11
+
12
+
- Session Replay: Add `Sentry.replay().pauseTouchTracking()` and `resumeTouchTracking()` to stop recording touches on sensitive screens, such as a custom PIN pad, while the screen recording continues. Touch tracking stays paused until `resumeTouchTracking()` is called, also for new replays and after `resume()` ([#6546](https://github.com/getsentry/sentry-java/pull/6546))
13
+
10
14
### Performance
11
15
12
16
- Most SDK log calls no longer allocate when `debug` is off ([#6600](https://github.com/getsentry/sentry-java/pull/6600))
0 commit comments