CODEWITHSUNDEEP
androidsharedpreferencesencrypted-shared-preference
Anurag
Anurag

Reputation: 3114

Using release candidate of android library security-crypto in production code

For one of the Android projects there is a need to store some values in Shared Preferences. For that I am planning to use EncryptedSharedPreferences

But when I checked, one of the library androidx.security:security-crypto on which this functionallity is dependent on is still not oficially released. Only release candidate version (1.0.0-rc03) is available

My question is - Is it fine to use this in production code? What are the chances that google might depriciate this library?

Upvotes: 0

Views: 234

Answers (1)

Dalmas
Dalmas

Reputation: 26557

Is it a common practice to use a release candidate version in production code? Yes, unfortunately. Is it a recommended practice? Of course not. But sometimes you don't have the choice, it's still better than trying to do encryption yourself.

In my opinion Google deprecating the library completely is very unlikely. And Android being open-source, at worst you can always copy the source code yourself in your project. This isn't the problem I would worry about, I would be more concerned about using a non-stable version of a cryptography library. But as I said, it may still be better than trying to do it yourself if there aren't any viable alternatives.

Upvotes: 1

Related Questions