tree 995d94359da2a85cfc3cb424be91701c385d4054
parent 4b7fd29ff16e38d48d921002bf9558efa17d5c21
author Riddle Hsu <riddlehsu@google.com> 1581005757 +0800
committer Riddle Hsu <riddlehsu@google.com> 1581934669 +0000

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: ActivityStackTests#testNavigateUpTo
Test: StartActivityTests#testStartActivityByNavigateUpToFromDiffUid
Test: Run the sample app in the bug link

Change-Id: I60732f430256d37cb926d08d093581f051c4afed