Fix back navigation in biometric enrollment.
Using the back buttons can cause a crash in at least two cases. Skipping face enrollment and then starting/stopping any enrollment can lead to an invalid token and failed HAT request. Backing out of the activity and restarting it can also lead to using a stale token that fails. Fix: 179336333 Test: manual on device Change-Id: I0c1133e4c3d9c97997043ddc9374aa3cfc4f1c97
This commit is contained in:
@@ -211,8 +211,7 @@ public class BiometricEnrollActivity extends InstrumentedActivity {
|
||||
case REQUEST_CHOOSE_LOCK:
|
||||
mConfirmingCredentials = false;
|
||||
if (resultCode == ChooseLockPattern.RESULT_FINISHED) {
|
||||
mGkPwHandle = BiometricUtils.getGatekeeperPasswordHandle(data);
|
||||
startMultiBiometricEnroll();
|
||||
startMultiBiometricEnroll(data);
|
||||
} else {
|
||||
Log.d(TAG, "Unknown result for chooseLock: " + resultCode);
|
||||
setResult(resultCode);
|
||||
@@ -222,8 +221,7 @@ public class BiometricEnrollActivity extends InstrumentedActivity {
|
||||
case REQUEST_CONFIRM_LOCK:
|
||||
mConfirmingCredentials = false;
|
||||
if (resultCode == RESULT_OK) {
|
||||
mGkPwHandle = BiometricUtils.getGatekeeperPasswordHandle(data);
|
||||
startMultiBiometricEnroll();
|
||||
startMultiBiometricEnroll(data);
|
||||
} else {
|
||||
Log.d(TAG, "Unknown result for confirmLock: " + resultCode);
|
||||
finish();
|
||||
@@ -283,7 +281,8 @@ public class BiometricEnrollActivity extends InstrumentedActivity {
|
||||
}
|
||||
}
|
||||
|
||||
private void startMultiBiometricEnroll() {
|
||||
private void startMultiBiometricEnroll(Intent data) {
|
||||
mGkPwHandle = BiometricUtils.getGatekeeperPasswordHandle(data);
|
||||
mMultiBiometricEnrollHelper = new MultiBiometricEnrollHelper(this, mUserId,
|
||||
mIsFaceEnrollable, mIsFingerprintEnrollable, mGkPwHandle);
|
||||
mMultiBiometricEnrollHelper.startNextStep();
|
||||
|
Reference in New Issue
Block a user