Release Samsung Privacy Display support 0.2.0#1
Draft
lech-kalinowski wants to merge 5 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Why
Samsung exposes Privacy Display through Knox Service Plugin managed configuration rather than a callable third-party app API. This release gives React Native applications useful standard Android protections while providing an accurate enterprise deployment path for eligible managed devices.
Developer impact
Applications can enable window capture protection, mark content as sensitive, inspect Samsung Privacy Display eligibility, obtain their Android package name, and generate validated KSP policy guidance without claiming direct control of the hardware feature.
Validation
npm test(4 tests passing)npm pack --dry-run(26 files; release metadata reports 0.2.0)