fix: break secure storage const paradox#48
Merged
TechAdeptRDD merged 1 commit intomainfrom Feb 21, 2026
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.
Motivation
conston secure storage option declarations but usingconsttriggersinvalid_constantbecauseflutter_secure_storageoption classes/enums are not compile-time constants.constso the options are runtime-initialized while preserving immutability withfinalto avoid the lint/runtime paradox.Description
static const AndroidOptions _androidOptions = ...tostatic final AndroidOptions _androidOptions = ....static final IOSOptions _iosOptions = const IOSOptions(...)withstatic final IOSOptions _iosOptions = IOSOptions(...).constfrom theFlutterSecureStorageinstantiation so the options are passed directly asaOptions: _androidOptionsandiOptions: _iosOptions.