Decisions and considerations. We are adding a new android x dependency for encrypted shared preferences. We have decided to use the interface of the long term stable version, like Okta and Stripe. This implementation choice was picked over the alternative of using shared preference with in-house crypto library (high risk and engineering effort) and migrating off shared preferences (high effort).
Risk of dependency conflicts are mitigated via using a version of the dependency used by other SDKs and also allowing devices running earlier versions of android to use the regular shared preferences.
Currently implementing with bump in minimum deploy target to SDK 23. Based on data on customers, we determined that the impacts are small.
only 0.4% of all historical users will be impacted
If we only consider users that were active in the last year, there will be an even smaller impact. in particular:
-- there are only 2 customer who have more than 100 users that will be impacted.
-- the percentage of users impacted for each customer is about 0.2%.
Added a fake key store to pass unit test per suggestion of (this is a workaround and there does not seem to be an offical support for AndroidKeyStore within the test suite)
KennyHuRadar
commented
9 months ago
Decisions and considerations. We are adding a new android x dependency for encrypted shared preferences. We have decided to use the interface of the long term stable version, like Okta and Stripe. This implementation choice was picked over the alternative of using shared preference with in-house crypto library (high risk and engineering effort) and migrating off shared preferences (high effort).
Risk of dependency conflicts are mitigated via using a version of the dependency used by other SDKs and also allowing devices running earlier versions of android to use the regular shared preferences.
Currently implementing with bump in minimum deploy target to SDK 23. Based on data on customers, we determined that the impacts are small.
Added a fake key store to pass unit test per suggestion of (this is a workaround and there does not seem to be an offical support for
AndroidKeyStorewithin the test suite)