-
Notifications
You must be signed in to change notification settings - Fork 52
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
Library crashing in devices running KitKat #6
Comments
Hi David, It should be safe SDK 19+, I will check in the next couple of days and release a new version with the correct version. |
Ah perfect! Thank you. |
Hi Patrik, can you please public release of this great lib with fixed min sdk? It causes problems in my app. Thanks in advance. Honza |
Meanwhile, you can force it in your manifest to avoid the merge errors: <uses-sdk android:minSdkVersion="19" tools:overrideLibrary="at.favre.lib:armadillo"/> |
Yep, thanks. I can only build my app with: But still app crashes on SDK 19 on start with: |
GCMParameterSpec is supposed to be available in devices running KitKat, but apparently, it's not implemented in all devices. IvParameterSpec can be used instead. Also, associated data is not available in Android KitKat. I've made a pull request with the fixes. |
Hey guys, thanks for new version 0.5.0, but crash still occurs with the same error on Kitkat as before, see:
|
0.5.0 did only change the minSDK, the fallback implementation for the GCM block mode is in progress (needed a fast release yesterday) |
fyi: This is going to be the next issue I'll tackle in the next couple of days. |
Hi Patric, |
@HonzaR sorry, since I do my open source projects in my spare time I cannot give you any ETA. You could fix it yourself however with only moderate effort. Just check out how @davidmigloz modified the
|
@patrickfav Thanks, but even with custom implementation of AesGsmEncryption I am getting same error, see:
I have implemented as @davidmigloz suggested and initialize as Do you have any idea? |
@HonzaR You will need to disable the associated Data on KitKat. That means adding to this code (for encrypt and decrypt)
the KitKat check
Note however that this will break the encrypted data if users upgrade from KitKat to anything newer. That is the reason the fix is not included as of yet, as Im not sure how to handle this special case. A workaround would be to force these users to use the kitkat version forever even after upgrade. |
Do you have any idea how to proceed with this? |
Hey, sorry for the radio silence, I was really swampt. Will tackle this in the next few days if nothing comes in between. |
PR is ready #31 |
Fixed with 0.6.0 |
According to the Readme:
But if you look into the
build.gradle
file, it declares:Are the docs not up to date? Or it is still safe to use the library with minSdkVersion = 19?
Thanks.
The text was updated successfully, but these errors were encountered: