diff options
| author | Sergey Nikolaienkov <sergeynv@google.com> | 2020-09-25 10:33:14 +0000 |
|---|---|---|
| committer | Sergey Nikolaienkov <sergeynv@google.com> | 2020-10-06 06:55:16 +0000 |
| commit | 48e47d1a2caff3c45ad8f0ec1559072052d7282d (patch) | |
| tree | 76b3d8846ffcb86d3e031b4e4e143e77b36b58b6 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 65f9099ad505984578c97c317a578f46abeb45b9 (diff) | |
Teach PackageManager to handle <required-(not-)feature>
Introducing 'required-feature' and 'requred-not-feature' tags that could
be used "inside" 'uses-permission' elements.
Elements of both types should have non-empty 'android:name' attribute to
specify the name of the feature.
If the 'uses-permission' element contains 'required-feature' and/or
'required-not-feature' elements, the permission will only be "requested"
if the system supports all the 'required-feature's and does not support
any of the 'required-not-feature's.
The new elemets are "replacement" of the existing
'android:required(Not)Feature' attributes that can be optionally added
to 'uses-permission' elements, but allow to specify only 1 feature each.
However the 'android:required(Not)Feature' attributes remain supported
for compatibility and will be treated similarly to the
'require-(not-)feature' elements.
Bug: 168079571
Test: make && flash
Test: atest CtsContentTestCases:PermissionFeatureTest
Change-Id: Id3043530ebac6bd11805a611cebbf08b45e12f68
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions