summaryrefslogtreecommitdiff
path: root/tools/dump-coverage/dump_coverage.cc
diff options
context:
space:
mode:
authorlumark <lumark@google.com>2019-09-14 19:25:21 +0800
committerlumark <lumark@google.com>2019-09-17 16:51:33 +0800
commitaf0629a53af2865b37ca459fc096bd2898503fcc (patch)
tree12eb4fd18373fb340b3bb57071c03e5c818c8501 /tools/dump-coverage/dump_coverage.cc
parent667db1bea529fad76a4fc57f58ef1e08b4432f7b (diff)
DO NOT MERGE 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 'tools/dump-coverage/dump_coverage.cc')
0 files changed, 0 insertions, 0 deletions