search

oblador / react-native-keychain

:key: Keychain Access for React Native
MIT License
3.12k stars 515 forks source link

6.1.0 could not load credentials, wrapped error: user not authenticated. Samsung S9/Android 10 #356

Open joelnewton opened 4 years ago

joelnewton commented 4 years ago

I was happy to see support for new biometrics face unlock and iris on Android but having tested the demo app on a Samsung Galaxy S9 with Android 10, which has both and fingerprint I was met with a User not authenticated error when loading credentials using either face or iris unlock. Fingerprint worked fine.

Has anyone else successfully used the 6.1.0 demo app with this device using face unlock or iris? or another which implements the same types?

Thanks,

hespresati commented 4 years ago

We have the same issue in some devices. It seems to be related to issue #318

joelnewton commented 4 years ago

We have the same issue in some devices. It seems to be related to issue #318

Thanks, yes I'm also watching that issue too. I've had to disable biometrics on Android for now owing to this.

etaiklein commented 3 years ago

We have the same issue in some devices. It seems to be related to issue #318

Thanks, yes I'm also watching that issue too. I've had to disable biometrics on Android for now owing to this.

@joelnewton Have you found any workarounds yet?

joelnewton commented 3 years ago

@etaiklein no, not yet sorry.

joelnewton commented 3 years ago

If there was an easy way to permit/support Fingerprint only and not support IRIS or Face unlock I'd be happy with that.

etaiklein commented 3 years ago

If there was an easy way to permit/support Fingerprint only and not support IRIS or Face unlock I'd be happy with that.

Yeah, even just passcode would be fine. Maybe downgrade to before iris/face was added?

whysetiawan commented 3 years ago

same here, any update on this?

etaiklein commented 3 years ago

I moved over to using expo-secure-store and expo-local-authentication in their bare workflow because their version of getSupportedBiometryType returns a list instead of a single type.

To my surprise they also had problems with the S10. Turns out this is an issue with Samsung itself.

this looks like a deeper issue at Samsung itself. At the moment, these devices are blacklisted from using fingerprint with the Biometric API. I'm not sure why, but it looks like its related to some vendor specific security implications.

See https://github.com/expo/expo/issues/7838#issuecomment-615486946 and https://github.com/expo/expo/issues/9500