ApexManager: Use new submitStagedSession API
This is a minimum change required to merge another CL in this topic, which will unblock merging it into AOSP. Change-Id: Ic1a80191e7ef17fb2e11e2ca6e2140131ac08e50 Merged-In: I5ea596ea6417825845c16bbb6e26e9c13845139b Bug: 136548037 Test: atest CtsStagedInstallHostTestCases
This commit is contained in:
@@ -312,10 +312,14 @@ class ApexManager {
|
||||
int sessionId, @NonNull int[] childSessionIds, @NonNull ApexInfoList apexInfoList) {
|
||||
if (!isApexSupported()) return false;
|
||||
try {
|
||||
return mApexService.submitStagedSession(sessionId, childSessionIds, apexInfoList);
|
||||
mApexService.submitStagedSession(sessionId, childSessionIds, apexInfoList);
|
||||
return true;
|
||||
} catch (RemoteException re) {
|
||||
Slog.e(TAG, "Unable to contact apexservice", re);
|
||||
throw new RuntimeException(re);
|
||||
} catch (Exception e) {
|
||||
Slog.e(TAG, "apexd verification failed", e);
|
||||
return false;
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user