-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Password does not work on Android API 33 #8
Comments
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. |
With 8b4e578 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 I'm not an Android developer... so I don't really understand the impact of That said, I tested both solution, and for my use case, |
@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 (android/security-samples#86), but with no resolution.
The same application works perfectly on Android API 32
The text was updated successfully, but these errors were encountered: