diff options
| author | lumark <lumark@google.com> | 2019-09-14 19:25:21 +0800 |
|---|---|---|
| committer | lumark <lumark@google.com> | 2019-09-17 20:59:27 +0800 |
| commit | f65e02d5183aa87fc914b5a0bc4aa0393eb0a95f (patch) | |
| tree | e22a23a66cae26fc9411c3ad08ef819965d92ea8 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | b77ae52cbca0395adffd99691a8bbe24f31c31a7 (diff) | |
Use realCallerId to check launch display for Bubbles
Since sysui is an entity that decides the App can launch Bubbles
thruogh PendingIntent, it would be make sense that using sysui's realCallerId
to check launch display.
But in RootActivityContainer#getLaunchStack will end up to check launch
display with PendingIntent creater's pid (-1) & uid, which won't pass
the check in the first place.
Add realCallerPid / realCallerUid in
RootActivityContainer#getLaunchStack for ActivityStarter to input
realCallerId to fix above scenario.
Fix: 138753287
Test: atest RootActivityContainerTests#testGetLaunchStackWithRealCallerId
Test: manual as below test steps:
1) Launch any app
2) Pop-up a Bubbles
3) In geusture nav mode, swping up app's activity to close and then press
Bubble icon to launch Bubble's activity quickly.
4) Expected app's activity should not shown.
Change-Id: Id3447f6a02f007b66932c59f6f9486688b1e8bad
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions