I am maintaining an app with relatively outdated versions of packages which includes flutter_secure_storage.
I am using 5.0.2 in my current setup. A requirement arose to update cipher algorithm AES_GCM_NoPadding. So I updated the package to 6.0.0 because this is the latest that our app can support without having issues with other dependencies.
Upon testing there is no problem when we're updating the algorithm. My only worry is that under the hood does my previously written values are updated to the new algorithm? as there is no information about it in the documentation only about encryptedSharedPreference.
I am maintaining an app with relatively outdated versions of packages which includes flutter_secure_storage.
I am using 5.0.2 in my current setup. A requirement arose to update cipher algorithm AES_GCM_NoPadding. So I updated the package to 6.0.0 because this is the latest that our app can support without having issues with other dependencies.
Upon testing there is no problem when we're updating the algorithm. My only worry is that under the hood does my previously written values are updated to the new algorithm? as there is no information about it in the documentation only about
encryptedSharedPreference
.Previous implementation (5.0.2):
FlutterSecureStorage();
After migration (6.0.0):
Thank you so much.