summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorKevin Chyn <kchyn@google.com>2018-09-27 17:28:20 -0700
committerKevin Chyn <kchyn@google.com>2018-10-01 15:00:30 -0700
commite741142569f5eaf8dcd49142d4c76d82b4edb47a (patch)
treede6d2cf4f0b9b545c570fae38abc0ff0c9bc1544 /tools/aapt2/java/JavaClassGenerator_test.cpp
parent914857349e66eb3ce4361c412797319ea0a24386 (diff)
Change BiometricManager#hasEnrolledBiometrics to canAuthenticate
BiometricPrompt#authenticate and BiometricManager#canAuthenticate now use the same logic to determine if the prompt can successfully be shown. Before Android P, apps used FingerprintManager isHwAvail && hasEnrolled before asking users to enable biometrics for their app. With BiometricPrompt, which abstracts away individual biometric modalities, developers need a way to determine if they should ask users to enable biometrics for their app. Having separate checks is a nightmare due to the untestable combinations of multi-biometric devices. This API change makes it much more scalable since the logic will be done in the platform. Fixes: 116823693 Test: manual test, returns status correctly Change-Id: Ie0ecd139c9a39100b6dbc9bd85462400cb465f08
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions