From a73bfa27a9a9dd4cf5eb4a7cf3b4feed6966e038 Mon Sep 17 00:00:00 2001 From: Kevin Chyn Date: Fri, 6 Dec 2019 12:02:00 -0800 Subject: [PATCH] Update BIOMETRIC_ERROR_VENDOR javadoc Bug: 142157673 Test: Builds Change-Id: I46f918806db3f50abfbe3aeb407f2e58e15edafd --- .../hardware/biometrics/BiometricConstants.java | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/core/java/android/hardware/biometrics/BiometricConstants.java b/core/java/android/hardware/biometrics/BiometricConstants.java index c8bf570e1bc80..191516b5b992a 100644 --- a/core/java/android/hardware/biometrics/BiometricConstants.java +++ b/core/java/android/hardware/biometrics/BiometricConstants.java @@ -86,12 +86,10 @@ public interface BiometricConstants { int BIOMETRIC_ERROR_LOCKOUT = 7; /** - * Hardware vendors may extend this list if there are conditions that do not fall under one of - * the above categories. Vendors are responsible for providing error strings for these errors. - * These messages are typically reserved for internal operations such as enrollment, but may be - * used to express vendor errors not otherwise covered. Applications are expected to show the - * error message string if they happen, but are advised not to rely on the message id since they - * will be device and vendor-specific + * OEMs should use this constant if there are conditions that do not fit under any of the other + * publicly defined constants, and must provide appropriate strings for these + * errors to the {@link BiometricPrompt.AuthenticationCallback#onAuthenticationError(int, + * CharSequence)} callback. OEMs should expect that the error message will be shown to users. */ int BIOMETRIC_ERROR_VENDOR = 8;