Update Settings together with generateChallenge/revokeChallenge
The internal implementation of generate/revoke in system_server is now asynchronous. To keep existing clients working, the manager classes introduce a blocking version of the generateChallenge calls. This change updates Settings to use the backward-compatible blocking calls. Bug: 157790417 Test: Enroll fingerprint/face Test: After enrollment, toggle setFeature or do subsequent enrollment in face/fingerprint settings Change-Id: Ib4dfdc5f12530b938ab9b1745f5a19cd9e2eceee
This commit is contained in:
@@ -135,7 +135,7 @@ final class SetNewPasswordController {
|
||||
|
||||
private Bundle getFingerprintChooseLockExtras() {
|
||||
Bundle chooseLockExtras = new Bundle();
|
||||
long challenge = mFingerprintManager.preEnroll();
|
||||
long challenge = mFingerprintManager.generateChallengeBlocking();
|
||||
chooseLockExtras.putInt(ChooseLockGeneric.ChooseLockGenericFragment.MINIMUM_QUALITY_KEY,
|
||||
PASSWORD_QUALITY_SOMETHING);
|
||||
chooseLockExtras.putBoolean(
|
||||
@@ -148,7 +148,7 @@ final class SetNewPasswordController {
|
||||
|
||||
private Bundle getFaceChooseLockExtras() {
|
||||
Bundle chooseLockExtras = new Bundle();
|
||||
long challenge = mFaceManager.generateChallenge();
|
||||
long challenge = mFaceManager.generateChallengeBlocking();
|
||||
chooseLockExtras.putInt(ChooseLockGeneric.ChooseLockGenericFragment.MINIMUM_QUALITY_KEY,
|
||||
PASSWORD_QUALITY_SOMETHING);
|
||||
chooseLockExtras.putBoolean(
|
||||
|
Reference in New Issue
Block a user