Grant shell MANAGE_PROFILE_AND_DEVICE_OWNERS permission
CTS tests will now need to call some provisioning
APIs that require MANAGE_PROFILE_AND_DEVICE_OWNERS,
this was previously avoided because CTS tests were
starting Managed Proviosing using a hacky way
to provision devices, we are now getting rid of this
as it was causing a lot of flakines. This is
part of bigger a plan to improve our testing
infrastructure.
Test: atest android.devicepolicy.cts.DevicePolicyManagerTest
Bug: 175392542
Change-Id: Id2e2f98f1d3785e45d8b94569bf9b30ae8c9f808
diff --git a/packages/Shell/AndroidManifest.xml b/packages/Shell/AndroidManifest.xml
index 5d6c4c3..a58ec65 100644
--- a/packages/Shell/AndroidManifest.xml
+++ b/packages/Shell/AndroidManifest.xml
@@ -120,6 +120,7 @@
<uses-permission android:name="android.permission.INTERACT_ACROSS_USERS_FULL" />
<uses-permission android:name="android.permission.CREATE_USERS" />
<uses-permission android:name="android.permission.MANAGE_DEVICE_ADMINS" />
+ <uses-permission android:name="android.permission.MANAGE_PROFILE_AND_DEVICE_OWNERS" />
<uses-permission android:name="android.permission.ACCESS_LOWPAN_STATE"/>
<uses-permission android:name="android.permission.CHANGE_LOWPAN_STATE"/>
<uses-permission android:name="android.permission.READ_LOWPAN_CREDENTIAL"/>