Open Rocketeer007 opened 1 year ago
I have made some commits that seem to fix the issue in Git. I need to perform more thorough testing on different android versions before releasing. If all goes well, I can have a release in 7 to 10 days. But you can build from source and try it out, if you can't wait that long: https://github.com/codenameone/FingerprintScanner
With https://github.com/codenameone/FingerprintScanner/commit/8b4e57846d5705eaa5140bd72d4fa8f7469f7094 it seems to be working well now. Want more time to test on other versions. Will make release next weekend.
Thank you @shannah @shai-almog for your commits about that. I saw that "setUserAuthenticationRequired" have not set on Android API 33 when keypair is generated. Could you please tell me why "setUserAuthenticationRequired" is not working on Android API 33 ? Thank you all.
Looking at the two commits recently added here, it seems that @shai-almog tried a solution of setUserAuthenticationValidityDurationSeconds(30)
, and @shannah instead removed setUserAuthenticationRequired(true)
I'm not an Android developer... so I don't really understand the impact of setUserAuthenticationRequired
. It would be really helpful if you could explain what this is doing, and why it's a better solution than setting a validity duration for the user authentication...
That said, I tested both solution, and for my use case, setUserAuthenticationRequired(false)
seems to work better; user authentication is still required, whereas with the other solution I still got some exceptions.
@shannah Any chance we can get a release that includes this fix?
@shai-almog @shannah Any chance of this being released in an official version of the FingerprintScanner library?
I have just released this on maven central as version 1.1.3. It is also updated in the Codename One settings if you update that way.
I have added the Fingerprint Scanner library to my Codename One project using the Maven dependency:
When calling
Fingerprint.addPassword(reason, key, value)
, the failure callback is triggered, with a very confusing exception.Searching for other instances of this online, I found a similar issue mentioned here (https://github.com/android/security-samples/issues/86), but with no resolution.
The same application works perfectly on Android API 32