[IMPROVEMENT] Refactor "Screenshot Deterrent" for Android #5447
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.
Description
Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions,
1. What is the reason for the change?
Both solutions for "Screenshot Deterrent" on iOS and Android have some inconsistencies regarding the screens it's activated. This refactor aims to improve this issue.
2. What is the improvement/solution?
Refactor the hook
useScreenshotDeterrent
to include Android's "Prevent Screenshot" solution.Screenshots/Recordings
Recording of Android behaviour after the refactor. The screen is black during screen share and/or recordings when it's displaying sensitive data (Android privacy feature).
android-recording.mov
Issue
Progresses https://github.com/MetaMask/mobile-planning/issues/227
Checklist