Replies: 2 comments 3 replies
-
|
hi @emil-st thanks for the informative post, I will be sure to check it and switch back to it after testing I also have plans to support 16kb and swift package manager soon |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
@ahmednfwela Thank you a lot! Appreciate your work on this! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion: Reconsidering FlutterSecureStorage in light of v10.0.0 major release
Hi OIDC maintainers! 👋
First, I want to say thank you for your excellent work on this library. The OIDC package has been incredibly helpful for our project, and we really appreciate your ongoing dedication to maintaining it.
Background
I noticed that starting from version 0.13.0, OIDC migrated from
flutter_secure_storagetosimple_secure_storage, with the reasoning thatflutter_secure_storageappeared to be unmaintained. This made complete sense at the time given the maintenance concerns.Recent Development
However, I wanted to bring to your attention that
flutter_secure_storagejust published version 10.0.0 (released December 11, 2024 - literally hours ago!). This is a huge major release with comprehensive improvements across all platforms:Key improvements include:
Android:
iOS/macOS:
flutter_secure_storage_darwinpackageWeb:
webpackage with js-interopuseSessionStorageparameterWindows:
Linux:
General:
FlutterSecureStorage().registerListener()The changelog shows active development with multiple beta releases (10.0.0-beta.1 through beta.5) addressing security issues, platform updates, and modernization efforts throughout 2024.
Question
Given this major revival and modernization of
flutter_secure_storage, would you be open to reconsidering its use in a future version of OIDC? I completely understand if there are technical reasons or architectural decisions that make this impractical, and I respect whatever direction you choose.I'm curious about your thoughts on this, especially since:
Our Context
We're currently using OIDC 0.12.1+2 in our B2C mobile application. We attempted to upgrade to 0.13.0, but unfortunately encountered a critical blocker: we were unable to publish our app to the Play Store because dependencies of
simple_secure_storagein that version used packages that don't pass Android's 16KB page size requirement.This 16KB page requirement is becoming increasingly important for Android apps, especially as Google enforces it for new devices. The inability to upgrade has left us in a difficult position, as we want to stay current with the OIDC package but are blocked by this platform compatibility issue.
With
flutter_secure_storagev10.0.0 now addressing Android compatibility (minimum SDK 23, updated to SDK 36, modern cipher implementations), it might offer a path forward that satisfies both security requirements and platform constraints.Understanding the long-term storage strategy would help us make informed decisions about our architecture and upgrade path.
Again, thank you for all your hard work, and I look forward to hearing your perspective on this! 🙏
References:
Beta Was this translation helpful? Give feedback.
All reactions