diff options
| author | Philip P. Moltmann <moltmann@google.com> | 2018-06-12 16:23:54 -0700 |
|---|---|---|
| committer | Philip P. Moltmann <moltmann@google.com> | 2018-06-19 12:23:55 -0700 |
| commit | 4a6dff091141e40df747f37203fb0fc17e16a39a (patch) | |
| tree | 8ce4bbaa12a4da0db887033ee74e65b722915718 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | fdc40f52d89769709c264a0c8f081ffc0ca8c87b (diff) | |
Allow permissions to have background permissions
Some permissions are getting split into foreground and background
variants. If an app only has the foreground version it can only access
the protected resource while the user is using it. Once the background
permission is added to the foreground permission the app can always
access the resource protected by the permission.
- Only having the background permission does grant anything.
- Mutliple foreground permission can share a single background permission,
but a foreground permission can not have multiple background
permissions.
- As the implementation of background permissions is based on AppOps
only the system can declare such foreground/background permissions
- A CTS test enforce that the background is in the same group as the
matching foreground permission.
Bug: 78788390
Test: Checked declared permission after boot and found new attributes
Change-Id: Ica7ba77b24345607c7467c41c982a58c39199024
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions