Skip to content
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

IllegalBlockSizeException after deleting a fingerprint on Android 8 #27

Open
jonknowles opened this issue Nov 14, 2017 · 5 comments
Open

Comments

@jonknowles
Copy link

I am getting the error message "Failed to encrypt the data with the generated key: IllegalBlockSizeException: null" when I save a credential in an app, delete the associated fingerprint, and try to use the credential again. After the point when I get the error, I can no longer add or verify fingerprint credentials in the app without re-installing. The error appears to be thrown from the onAuthenticated method of FingerprintAuth.java.

It would be nice if after deleting a fingerprint with credentials associated with it and then adding a new one, new credentials using the new fingerprint could then be saved over the old ones.

@jonknowles jonknowles changed the title IllegalBlockSizeException after deleting a fingerprint on Android IllegalBlockSizeException after deleting a fingerprint on Android 8 Nov 14, 2017
@koenvanzuijlen
Copy link

Also experiencing this, did you ever find a fix? @jonknowles

@jonknowles
Copy link
Author

Nope, didn't find a fix, unfortunately.

@raphaelratuczne
Copy link

This error occurs on android 8, in my code I have to verify for do not show the option in this version. Works normally on android 7. I am waiting a fix to update my code.

@damirarh
Copy link

damirarh commented Feb 2, 2018

I created a PR #31 with a fix which works for me. Maybe it will be useful for someone else even if it never gets merged. More details in the PR itself.

@dais-set
Copy link

dais-set commented Aug 8, 2018

Hi @damirarh thanks for your fix! We can confirm it also works for us (tested on oneplus 3 with latest oreo). We hope the fix makes it into the master branch but we are making our own branch in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants