You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that androidx.security:security-crypto is officially deprecated, and the release notes say "Deprecated all APIs in favour of existing platform APIs and direct use of Android Keystore", will there be support for Android Keystore in the future? EncryptedSharedPreferences is working for me currently but I worry about potential issues down the line.
Or is it even worth it using EncryptedSharedPreferences in the first place and just use SharedPreferences? Also even considering a wrapper that uses Keystore to manually encrypt/decrypt the value before calling putString().
A fork of security-crypto now exists if you still have need of EncryptedSharedPreferences. There's also an encrypted-datastore you can use. I prefer to leave it to users to swap in implementations like those which are more general purpose rather than implement and maintain new keystore logic.
Now that androidx.security:security-crypto is officially deprecated, and the release notes say "Deprecated all APIs in favour of existing platform APIs and direct use of Android Keystore", will there be support for Android Keystore in the future? EncryptedSharedPreferences is working for me currently but I worry about potential issues down the line.
Or is it even worth it using EncryptedSharedPreferences in the first place and just use SharedPreferences? Also even considering a wrapper that uses Keystore to manually encrypt/decrypt the value before calling putString().
https://developer.android.com/jetpack/androidx/releases/security#version_110_2
https://developer.android.com/privacy-and-security/cryptography#jetpack_security_crypto_library
The text was updated successfully, but these errors were encountered: