From 0fdb3a84cfd722c994ab693cfef3edc2a51f3115 Mon Sep 17 00:00:00 2001 From: Christopher Tate Date: Fri, 3 Mar 2017 17:18:20 -0800 Subject: [PATCH] Fix bug #35673706 - null verifier component... ...causing an NPE when we attempted to call getPackageName() on it. This patch avoids the NPE, but does not address the underlying question of why the component we're attempting to target is coming back null. This new approach guarantees the security of the broadcast, though, so we needn't worry further about that. Test: install app & note verifier action Change-Id: I0d316e0815210ba1fbb14da6b76d5c23a85c96a4 --- .../core/java/com/android/server/pm/PackageManagerService.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/core/java/com/android/server/pm/PackageManagerService.java b/services/core/java/com/android/server/pm/PackageManagerService.java index 1fe4ccca765e1..d127e23852689 100644 --- a/services/core/java/com/android/server/pm/PackageManagerService.java +++ b/services/core/java/com/android/server/pm/PackageManagerService.java @@ -14767,7 +14767,7 @@ public class PackageManagerService extends IPackageManager.Stub { */ verification.setComponent(requiredVerifierComponent); idleController.addPowerSaveTempWhitelistApp(Process.myUid(), - requiredVerifierComponent.getPackageName(), idleDuration, + mRequiredVerifierPackage, idleDuration, verifierUser.getIdentifier(), false, "package verifier"); mContext.sendOrderedBroadcastAsUser(verification, verifierUser, android.Manifest.permission.PACKAGE_VERIFICATION_AGENT,