Simplify library set up by declaring activities internally #620
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.
Changes
Before this PR, when a developer wanted to use this library, they would need to declare the Lock activities in the
AndroidManifest.xml
file.Following what the SDK does, this PR will declare both Classic and Passwordless lock required activities, which will be merged in the final
AndroidManifest.xml
file. This also applies to the "Internet" permission.This change effectively reduces the changes required to use the library, removing the need to modify the manifest file.
This is not a breaking change, but developers are encouraged to remove the activities declaration from their manifest files to reduce the possibility of duplicated intent filter declarations (no harm).
References
None
Testing
Manually tested