Fix NPE caused by null replacedPkgSetting

replacedPkgSetting can be null if the existing package has been removed around the same time it was updated, because we only acquire mLock at the commit stage. Adding an NPE check to prevent crashes.

BUG: 403742230
FIXES: 403742230
Test: builds
Change-Id: I361836d6960fdde75357c09077ba3c382ec8a7bb

parent 34eaed1a

services/core/java/com/android/server/pm/InstallRequest.java

+3 −0

Original line number	Diff line number	Diff line
		@@ -869,6 +869,9 @@ final class InstallRequest {
		public void setScannedPackageSettingFirstInstallTimeFromReplaced(
		@Nullable PackageStateInternal replacedPkgSetting, int[] userId) {
		assertScanResultExists();
		if (replacedPkgSetting == null) {
		return;
		}
		mScanResult.mPkgSetting.setFirstInstallTimeFromReplaced(replacedPkgSetting, userId);
		}