UM.getUserHandle -> UM.getProcessUserId

UM is being made @UserHandleAware, so using an explicit method avoids ambiguity.

Bug: 201679968

Test: (No-op) compiles and treehugger
Change-Id: If067af7ced5017a9689cafbf99ceec1d26c06b3b
This commit is contained in:
Adam Bookatz
2021-10-01 00:15:32 -07:00
parent e959dc02ab
commit 30dafd4140
7 changed files with 10 additions and 15 deletions

View File

@@ -301,8 +301,8 @@ public abstract class AppStateAppOpsBridge extends AppStateBaseBridge {
if (entries == null) {
return 0;
}
final ArrayMap<String, PermissionState> entriesForProfile = entries.get(mUserManager
.getUserHandle());
final ArrayMap<String, PermissionState> entriesForProfile =
entries.get(mUserManager.getProcessUserId());
if (entriesForProfile == null) {
return 0;
}
@@ -316,8 +316,8 @@ public abstract class AppStateAppOpsBridge extends AppStateBaseBridge {
}
loadPermissionsStates(entries);
loadAppOpsStates(entries);
final ArrayMap<String, PermissionState> entriesForProfile = entries.get(mUserManager
.getUserHandle());
final ArrayMap<String, PermissionState> entriesForProfile =
entries.get(mUserManager.getProcessUserId());
if (entriesForProfile == null) {
return 0;
}