CustomAndroidUI will not use device password to authenticate, here's whySee original GitHub issue
onSuccessWithManualPassword was intended to be used when the developer will manually maintain
a separate app password. Which he will compare.
So you would want to
resolve(password) here, https://github.com/EddyVerbruggen/nativescript-fingerprint-auth/blob/7ab2ddef09204320ae9db8bf40312685d6bfe72b/src/fingerprint-auth.android.ts#L117
but by doing so, the functionality of using password won’t be same between using and not using custom UI.
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
That’s up to your app to make clear, I guess.
Hey @shiv19, thanks for reporting this!
I always assumed that password entry widget of the custom UI was similar to the one on the default UI, but it turns out the custom UI relies on a custom password the user needs to configure for the app (instead of using the system-wide password).
For a number of reasons, I think the best solution is to just
resolve(password). I’ve added this to the demo app and the readme.