bug: Biometric Plugin not returning right value when Fingerprint not enabled on Android

[fortivait]

Version

7.1.7

Platform(s)

• Android
• iOS
• Web

Current behavior

On Android Device when Face is enabled, but Finger print is disabled we are getting value as 3.
Any known reported issues on this ?
We have upgraded to "@capgo/capacitor-native-biometric": "7.1.7"
From: "@capgo/capacitor-native-biometric": "6.0.1",

irrespective of face_authentication enabling status if fingerprint is not enabled then getting Biometry isAvailable object as : {"isAvailable":false,"biometryType":0, "errorCode": 3}
if fingerprint is available then getting Biometry isAvailable object as : {"isAvailable":true,"biometryType":6}

Expected behavior

Excpect to show Face as its enabled

Reproduction

No response

Steps to reproduce

Testing app upgrade from 6 to 7

Other information

No response

Capacitor doctor

cap doctor output adding

Before submitting

• I have read and followed the bug report guidelines.
• I have attached links to possibly related issues and discussions.
• I understand that incomplete issues (e.g. without reproduction) are closed.

Fastest way to fix this issue

• I want to get this fix ASAP and found the issue with Algora we recommend ($50 to $500)

[fortivait]

Same happens with 7.1.13 as well

[fortivait]

7.1.6 version is where this issue started.
7.1.1 and 7.1.2 we are getting isAvailable as true but verifyIdentity method is failing and crashing the app

[WcaleNieWolny]

Can you please tell me what phone do you use?

[WcaleNieWolny]

Hello, I can confirm that on one of my phones this problem also occurs. According to ChatGPT, on some devices, the face is not considered to be "safe" (level 3, secure). This is why it fails to detect it. Try using useFallback with isAvailable to see if it fixes it.

[ToriChanIntegration]

Thanks for the report — and the extra confirmation from others, super helpful 🙏

What you’re seeing can happen on Android devices where face unlock is not exposed as Class 3 (strong) biometrics. In that case, isAvailable may return unavailable for the “strong biometric” path even if face unlock exists in device settings.

Could you share:

1. Exact device model(s) + Android version(s)
2. Whether PIN/pattern fallback is enabled
3. Output of both isAvailable() and verifyIdentity({ useFallback: true })

If fallback succeeds while isAvailable reports unavailable, that strongly points to device/security-class behavior rather than plugin failure. If you post those values, we can decide whether docs/API should better distinguish “strong biometric available” vs “some auth available”.