diff options
| author | Philip P. Moltmann <moltmann@google.com> | 2018-12-20 10:38:18 -0800 |
|---|---|---|
| committer | Philip P. Moltmann <moltmann@google.com> | 2018-12-20 14:04:52 -0800 |
| commit | 125c6eee6a87af683d7462a414b72cb5cdc1d318 (patch) | |
| tree | a5399a22b0afedcdbe643723999727e344cf2241 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 5acec68de4f998c38e0e8cb31e280171c6c4cfcf (diff) | |
Only set MODE_FOREGROUND when fg app is granted
This changes the code path where we have a pre-Q app that declared a
location permissions. In this case the background permission is added as
an implicit permission.
We never want to automatically extend the grant to the background
permission. I.e. If the original permission is granted, we want to switch to
foreground mode.
If the original permission is revoked, the app-ops
state does not matter as everybody is supposed to check for both
permission and app-op. Still, setting the app-op to foreground is
confusing. Let's not do this.
Test: Looked at app-ops state that ...
- targets pre-Q
- requests location
- does not get any permissions pregranted
... and verified that no app-op is set after fresh boot
Change-Id: Ic0a6feba98ca553a1ff66cdc348ceb2ca40217ee
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions