[pm] properly clean up early install failures

Basically a no-op, but still worth fixing to avoid confusions. Currently
we don't cleanup the code path if the early install stages fail.

The issue was there even before ag/19246346, so I am not sure if it's a
recent regression. Most of the time, install failure is from copyApk, which
means it doesn't matter if we don't clean up the code path, as it will
be empty anyway. The other failure case would be if
copyNativeBinariesWithOverride fails, but if it does, the verify() stage
of the installation would have failed too, so we wouldn't come to this
code path anyway.

BUG: 259470449
Test: manual
Change-Id: I378268bb39bc0d6ab8b301225720273ec100bba4
This commit is contained in:
Songchun Fan
2023-01-30 14:59:11 -08:00
committed by Song Chun Fan
parent 83c4c5dab2
commit 0274c1b0f9

View File

@@ -525,13 +525,13 @@ class InstallingSession {
}
private void processApkInstallRequests(boolean success, List<InstallRequest> installRequests) {
if (success) {
if (!success) {
for (InstallRequest request : installRequests) {
if (request.getReturnCode() != PackageManager.INSTALL_SUCCEEDED) {
cleanUpForFailedInstall(request);
}
}
} else {
mInstallPackageHelper.installPackagesTraced(installRequests);
for (InstallRequest request : installRequests) {