tree b0c6f14ed96d6bc99979415b705f3881f8ca8531
parent a08b16989742a8d2e520500fb3f21ab5cd17863f
author Edgar Wang <edgarwang@google.com> 1649237427 +0800
committer Android Build Coastguard Worker <android-build-coastguard-worker@google.com> 1652735559 +0000

Fix LaunchAnyWhere in AppRestrictionsFragment

If the intent's package equals to the app's package, this intent
will be allowed to startActivityForResult.
But this check is unsafe, because if the component of this intent
is set, the package field will just be ignored. So if we set the
component to any activity we like and set package to the app's
package, it will pass the assertSafeToStartCustomActivity check
and now we can launch anywhere.

Bug: 223578534
Test: robotest and manual verify
Change-Id: I40496105bae313fe5cff2a36dfe329c1e2b5bbe4
(cherry picked from commit 90e095dbe372f29823ad4788c0cc2d781ae3bb24)
(cherry picked from commit 019eb77224b0671458ad447f15a2a29935c866c6)
Merged-In: I40496105bae313fe5cff2a36dfe329c1e2b5bbe4