Update to latest Flutter Secure Storage - #1761
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates to the latest stable release of flutter_secure_storage 10.0.0 which deprecates encryptedSharedPreferences on Android.
This PR also adds
first_unlock_this_deviceas an IOS option instead of the defaultunlockedsetting - this ensures that secure storage can be accessed by background tasks while the device is unlocked.The startup warning message is also updated to NOT ask the user to uninstall the app.
This should fix issues with app start up that we have been facing over the past month.