-
Notifications
You must be signed in to change notification settings - Fork 11
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
android.security.KeyStoreException: Invalid operation handle #235
Comments
It looks like a platform bug. I'm closing it. I have not found "Invalid operation handle" in the source code. |
Hello, In my app, the combo "IllegalBlockSizeException" caused by "android.security.KeyStoreException: Invalid operation handle" happens because the Cipher classes used with Keystore keys are not thread safe. -Synchronizing only calls to doFinal() did not help |
Hello @f4grx
|
I tested on 3 of my phones: So it may be quite common. I did not test other phones but I am reasonably sure most of them have the same issues. |
Yes, this is the page that gave me the idea of Cipher synchronization. But who really provides this implementation? Is it really Samsung? I may have seen mentions of BouncyCastle. The Pixel2 is made by HTC and lineage possibly don't use any Samsung code. |
We have one more issue like this. Some devices with LineageOS have a problem with encryption/decryption. Unfortunately, I don't have any devices with LineageOS yet. But I have Nexus 4(I know it's an old device :)) and I'm going to install LineageOS. Then I'll be able to test the app. |
I've tested the app on different versions of LineageOs. Unfortunately, I've received no errors. The app works well. So I still can't reproduce such errors. I've made the decryption block as synchronized. I hope these changes will solve the problem (or give me more details) |
The text was updated successfully, but these errors were encountered: