tree 9f045ee87b25db03e75e0a72359490bb4826a645
parent 41c009d1729c88868d3f7b937e7f508b920aab93
author Riddle Hsu <riddlehsu@google.com> 1583217381 +0800
committer Riddle Hsu <riddlehsu@google.com> 1583221081 +0000

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:com.android.server.am.ActivityStackTests
Change-Id: I60732f430256d37cb926d08d093581f051c4afed