-
Notifications
You must be signed in to change notification settings - Fork 97
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
java.lang.IllegalArgumentException: key.length == 0 #22
Comments
Android 4.4.4 in genymotion emulator. |
Hey @AlvaroBro can you please provide details of how I might try to reproduce this? |
Hi, yes sure I will do so eventually when I have some extra time. Thanks! |
I had an incoming crash report showing the same, only from one user so far. Since it this report was sent in via an SDK, I unfortunately have no reproduction steps. Device: Samsung SM-G313HN |
@matthew-niemann , basically I could reproduce this using some unit tests in API 21. During debug I noticed that the prefs contained the hash of the ALIAS therefore one could not generate the AESKey and next time when it was needed it was not there. Therefore, the problem. I fixed it by just changing to a new prefs name. |
@RobartGmbH so it happens when you change the device security (PIN/Password) and open the app after that? I am trying to understand if it's happening coz the recovery is failing to generate new keys. |
When initializing the library I got this situation: it will fail to init due to IllegalArgumentException.
I was doing some tests regarding recovery after a keystore deletion due to unlock pattern/pin/password changes. Usually the recovery was as expected, but one of the times it got stuck in this situation, and only reinstalling the app would fix it.
The text was updated successfully, but these errors were encountered: