Merge "Throw an exception in RoR api on no-pin case" am: 7444774737 am: 4d208ac97e

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1584516

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: Ic6399b2d5de8fdca4973c8cf4a435c22ba0e68d8
This commit is contained in:
Tianjie Xu
2021-02-23 23:58:41 +00:00
committed by Automerger Merge Worker

View File

@@ -26,6 +26,7 @@ import android.annotation.RequiresPermission;
import android.annotation.SuppressLint; import android.annotation.SuppressLint;
import android.annotation.SystemApi; import android.annotation.SystemApi;
import android.annotation.SystemService; import android.annotation.SystemService;
import android.app.KeyguardManager;
import android.app.PendingIntent; import android.app.PendingIntent;
import android.compat.annotation.UnsupportedAppUsage; import android.compat.annotation.UnsupportedAppUsage;
import android.content.BroadcastReceiver; import android.content.BroadcastReceiver;
@@ -631,10 +632,15 @@ public class RecoverySystem {
/** /**
* Prepare to apply an unattended update by asking the user for their Lock Screen Knowledge * Prepare to apply an unattended update by asking the user for their Lock Screen Knowledge
* Factor (LSKF). If supplied, the {@code intentSender} will be called when the system is setup * Factor (LSKF). If supplied, the {@code intentSender} will be called when the system is setup
* and ready to apply the OTA. This API is expected to handle requests from multiple clients * and ready to apply the OTA. <p>
* simultaneously, e.g. from ota and mainline.
* *
* <p> The behavior of multi-client Resume on Reboot works as follows * <p> If the device doesn't setup a lock screen, i.e. by checking
* {@link KeyguardManager#isKeyguardSecure()}, this API call will fail and throw an exception.
* Callers are expected to use {@link PowerManager#reboot(String)} directly without going
* through the RoR flow. <p>
*
* <p> This API is expected to handle requests from multiple clients simultaneously, e.g.
* from ota and mainline. The behavior of multi-client Resume on Reboot works as follows
* <li> Each client should call this function to prepare for Resume on Reboot before calling * <li> Each client should call this function to prepare for Resume on Reboot before calling
* {@link #rebootAndApply(Context, String, boolean)} </li> * {@link #rebootAndApply(Context, String, boolean)} </li>
* <li> One client cannot clear the Resume on Reboot preparation of another client. </li> * <li> One client cannot clear the Resume on Reboot preparation of another client. </li>
@@ -658,6 +664,13 @@ public class RecoverySystem {
if (updateToken == null) { if (updateToken == null) {
throw new NullPointerException("updateToken == null"); throw new NullPointerException("updateToken == null");
} }
KeyguardManager keyguardManager = context.getSystemService(KeyguardManager.class);
if (keyguardManager == null || !keyguardManager.isDeviceSecure()) {
throw new IOException("Failed to request LSKF because the device doesn't have a"
+ " lock screen. ");
}
RecoverySystem rs = (RecoverySystem) context.getSystemService(Context.RECOVERY_SERVICE); RecoverySystem rs = (RecoverySystem) context.getSystemService(Context.RECOVERY_SERVICE);
if (!rs.requestLskf(context.getPackageName(), intentSender)) { if (!rs.requestLskf(context.getPackageName(), intentSender)) {
throw new IOException("preparation for update failed"); throw new IOException("preparation for update failed");