You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the backupJSONObjectToStorage function to store my secret and when i try to get the secret using loadBiometricSecret function and trying to use Pin instead of Fingerprint i am getting 'biometric_success' in the success callback of loadBiometricSecret instead of the secret.
Expected would be get the secret in the success callback.
Plugin version: 4.0.2
Cordova : 9.0.0
Cordova Android : ^9.0.0
Device: One Plus 7 (Android 11)
The text was updated successfully, but these errors were encountered:
I am also facing the same issue @Kawinesh . loadBiometricSecret and registerBiometricSecret is not working properly with PIN authentication. I think we should not give option to use PIN to perform any operation with these two methods. I suspect setting and getting secret from keyChain works only with biometric(fingerprint/touchId) authentication. However we can allow to use PIN if user just calls show method as it just authenticates identity and it doesn't deal with any secret operation.
If we add the below highlighted line in If condition then it will stop giving option to use pin If the operation is apart from justAuthenticate
@NiklasMerz please let me know if this solution is fine then I will raise the PR for this change.
NOTE: after doing this changes I have tested and I am able to achieve as expected.
Bug report
Description
I am using the backupJSONObjectToStorage function to store my secret and when i try to get the secret using loadBiometricSecret function and trying to use Pin instead of Fingerprint i am getting 'biometric_success' in the success callback of loadBiometricSecret instead of the secret.
Expected would be get the secret in the success callback.
Plugin version: 4.0.2
Cordova : 9.0.0
Cordova Android : ^9.0.0
Device: One Plus 7 (Android 11)
The text was updated successfully, but these errors were encountered: