diff options
| author | 2022-11-10 16:33:30 +0000 | |
|---|---|---|
| committer | 2022-12-21 16:05:22 +0000 | |
| commit | d92605d2fb776f715a914eeb769a8ff683a50f01 (patch) | |
| tree | 60d328416cd403f53163274e86371bff23774eea /libs/androidfw/AssetsProvider.cpp | |
| parent | 55cac928498b2a445f26d2c591792d312296230b (diff) | |
Update ASM clearTask Logging
As part of go/activity-security, we introduced logging on finishActivity
in ag/19950589. This will be used to decide if we can block an activity
from finishing it's task if it is not on top of it's stack.
A case was missed - apps can also clearTask through
`appTask.finishAndRemoveTask()`, which follows a different code path.
To include this, and centralise the code, logging has been moved a level
down, and callerUid passed through where needed.
There are other callers as well, i.e from RecentTasks.java, but they
already enforce MANAGE_TASKS permission, so I've tried to minimise
callerUid having to be passed through from there for these other cases.
Bug: 246738504
Test: statsd_testdrive 495
Test: Manually reproduced scenario and checked logs
Change-Id: Ibc5b830217d6219cb8a0e620bf800c1ffa7a52a3
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions