What do you mean? Our team is concerned now

[tieorange]

https://github.com/Salat-Cx65/AdvancedBiometricPromptCompat/blob/fa9036476aa6e6ef626fbc1d47f8b9a76b379eba/biometric/src/main/java/dev/skomlach/biometric/compat/utils/hardware/Android28Hardware.kt#L268

[sergeykomlach]

It's a bit outdated comment, but still can be valid - I'll check ASAP.
On 'pure' API28 implementation (built-in BiometricPrompt API) is no way to get 'isBiometricEnrolled' results for specific biometric, like Iris/Face, etc.
So, some tricks have used that try to determine by indirect signs which biometric data are used (like "if NOT fingerprint BUT something enabled in the System Settings").
There are edge cases where we cannot tell exactly what type of biometrics is registered - for example, if it is Samsung with Face and Iris - in this case, the code can give a false-positive result. It can happen if you set BiometricApi.BIOMETRIC_API + BiometricType.BIOMETRIC_FACE or BiometricApi.BIOMETRIC_API + BiometricType.BIOMETRIC_IRIS

Fortunately, for Samsung with Face and Iris, the 'legacy' check should work correctly, so for general cases when you use BiometricApi.AUTO/LEGACY_API + BiometricType.BIOMETRIC_FACE/BIOMETRIC_IRIS all should work fine.

[sergeykomlach]

I made few changes in the library, also add the new section to the README
https://github.com/Salat-Cx65/AdvancedBiometricPromptCompat#false-positive-andor-false-negative-detection

[tieorange]

Thanks mate!