tag 50a1c631514e7350afcf25cc77de3f6149579c31
tagger The Android Open Source Project <initial-contribution@android.com> Mon May 04 09:45:59 2020 -0700
object 4a9623adbc952af990d361bc92336f688c0f045c

Android 8.0.0 release 46

commit 4a9623adbc952af990d361bc92336f688c0f045c
author Riddle Hsu <riddlehsu@google.com> Tue Mar 03 14:36:21 2020 +0800
committer Anis Assi <anisassi@google.com> Mon Mar 30 13:32:35 2020 -0700
tree c5298bbe1726b1808eaec3e543f711c418afd5d2
parent c10ac9677a4557409f6122d0dd93253363ca1a5d

RESTRICT AUTOMERGE Use consistent calling uid and package in navigateUpTo

Originally, if the caller of navigateUpTo is alive, even the calling
uid is set to the caller who launched the existing destination activity,
the uid from caller process has higher priority to replace the given
calling uid. So this change doesn't modify the existing behavior if
the caller process is valid. Besides, the case of delivering new intent
uses the source record as calling identity too, so the case of starting
new activity should be consistent.

Also forbid attaching null application thread to avoid unexpected state
in process record.

Bug: 144285917
Test: bit FrameworksServicesTests:ActivityStackTests
Test: bit CtsSecurityTestCases:ActivityManagerTest# \
      testActivityManager_attachNullApplication
Merged-In: I60732f430256d37cb926d08d093581f051c4afed
Change-Id: I60732f430256d37cb926d08d093581f051c4afed
(cherry picked from commit 1c9bf5cc54d0b32d8f3046c452e710b017c477c0)