[romtsn]

📜 Description

Adds Sentry.replay().pauseTouchTracking() and Sentry.replay().resumeTouchTracking(). While touch tracking is paused, ReplayIntegration drops touch events, but the masked screen recording continues. This works in both session and buffer mode, so a buffered replay that is sent later also has no touches for that period.

Sentry.replay().pauseTouchTracking() // before showing the PIN pad
Sentry.replay().resumeTouchTracking() // after it is hidden

Behavior worth reviewing:

• The flag is independent of pause()/resume(). resume() does not resume touch tracking, and resumeTouchTracking() does not record touches while the replay is paused.
• Only resumeTouchTracking() clears the flag. start(), stop() and new app sessions keep it, so touches cannot leak by accident. This is different from pause(), which an explicit start() resets.
• The flag is set directly (@Volatile) instead of through enqueueOnMainThread like the lifecycle commands. It does not touch ReplayState, so its order relative to lifecycle commands does not matter, and a queued set could let touch events that are already pending on the main looper through.
• Breadcrumbs are not affected. beforeBreadcrumb already covers them.

Also marks debugMaskingEnabled as @Volatile, because it is written on the caller's thread and read on the recorder thread.

💡 Motivation and Context

Masking hides sensitive content such as a custom PIN pad or a masked WebView, but the recorded touch positions can still reveal the input. pause() already stops touches, but it also stops the screen recording, which some apps want to keep.

The same API comes to sentry-cocoa in a parallel PR. Hybrid SDKs follow later.

• resolves: [Session Replay] Add ability to mask or suppress touch input over sensitive views and WebViews #5787
• resolves: JAVA-658

💚 How did you test it?

Unit tests in ReplayIntegrationTest: touches are dropped while screenshots continue, resume() does not resume touch tracking, resumeTouchTracking() waits for resume(), and the flag carries over to new replays, also when it is set before any replay starts.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

• Docs: docs(replay): Document pausing touch tracking on mobile sentry-docs#20711
• Expose the API in the React Native and Flutter SDKs.

🤖 Generated with Claude Code

[linear-code]

JAVA-658

[runningcode]

Nice!

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 811035c

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.64.0 (1)	release

⚙️ sentry-android Build Distribution Settings