From cf7fe46dafdda00d6f7084b2ea13d561722504c1 Mon Sep 17 00:00:00 2001 From: Kevin Chyn Date: Tue, 10 Mar 2020 17:23:47 -0700 Subject: Update ACTION_BIOMETRIC_ENROLL documentation Activity result codes are already being used "undocumentedly" by SUW. Given the timeline, it's better to not make any guarantees about the result code and just mention that applications should still check BiometricManager#canAuthenticate(int) after onActivityResult. Fixes: 151058692 Test: Skip fingerprint in SUW. Fingerprint SUW is not shown again. Change-Id: Ia36ea1b6cfc39848be00f8d2219604e68ff45213 --- core/java/android/provider/Settings.java | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/core/java/android/provider/Settings.java b/core/java/android/provider/Settings.java index 641de4a71142..d99844e62a2e 100644 --- a/core/java/android/provider/Settings.java +++ b/core/java/android/provider/Settings.java @@ -709,10 +709,7 @@ public final class Settings { * If not specified, the default behavior is * {@link android.hardware.biometrics.BiometricManager.Authenticators#BIOMETRIC_WEAK}. *

- * Output: Returns {@link android.app.Activity#RESULT_CANCELED} if the user already has an - * authenticator that meets the requirements, or if the device cannot fulfill the request - * (e.g. does not have biometric hardware). Returns {@link android.app.Activity#RESULT_OK} - * otherwise. Note that callers should still check + * Output: Nothing. Note that callers should still check * {@link android.hardware.biometrics.BiometricManager#canAuthenticate(int)} * afterwards to ensure that the user actually completed enrollment. */ -- cgit v1.2.3-59-g8ed1b