Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CustomAndroidUI will not use device password to authenticate, here's why

See original GitHub issue

https://github.com/JesusM/FingerprintManager/blob/333e4ca4e44d5c5fb725e8926690000d926af880/javasample/src/main/java/com/jesusm/fingerprintmanager/javasample/MainActivity.java#L74

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.

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

EddyVerbruggencommented, Aug 9, 2018

That’s up to your app to make clear, I guess.

2reactions

EddyVerbruggencommented, Aug 9, 2018

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.