This permission is required to query AppPredictionService.
When the unbundled Chooser doesn't request this permission,
we get a SecurityException attempting to invoke
createPredictionSession(). When we request the permission
but don't add it to this allow-list, the device boot-loops.
With the permission added in both places (and some other
local changes), the unbundled Chooser is able to show the
full set of app predictions.
Test: Manual, as described above.
Bug: 206831012
Change-Id: I154d0555471f7f8820ac151b77a61cb8d9bf7603
These two permissions are required for the most basic
ChooserActivity flows (as determined by runtime exceptions
during prototyping). Without this allow-listing, the
unbundled chooser's intent resolvers fail to register at
startup, and the device boot-loops.
Among the privileges that might require allow-listing,
these two in particular were sufficient for showing a
basic Chooser UI and launching the user-selected target.
More complex Chooser flows may turn out to require
additional permissions later on.
Test: manual testing as described above, but requires
several local-only changes to exercise the flow, and
this CL has to be the first to go in (but has no
side-effects of its own).
Change-Id: I6a24a46a91199e8b3fb643f047a9b9412b19eb8d
