Open russhwolf opened 2 years ago
This is NOT blocked by #71. There are currently no known issues, just a lack of testing and feedback.
Switched out NSUserDefaultSettings with KeychainSettings. I've tried using it once, got the feedback that it wasn't working. Like the values weren't persisted. Didn't look into it again though. Could be something on my side as well. Lazy: Is there anything that needs to be enabled on iOS side in order to use the Keychain?
There shouldn't be any extra config necessary. The sample app has an option to use it so maybe compare against that.
Just wondering if KeychainSetting
would also implement ObservableSettings
in the future as well?
See #71. Unfortunately, I'm not aware of a way to observe keychain updates that works outside of macOS.
Just to let you know we use KeychainSettings
in one of our projects and it works nicely!
Can't this be closed since 1.0.0 is released?
It's still marked experimental in 1.0.0
Using KeychainSettings
in a project at the moment, providing a couple extra default properties (kSecAttrAccessible
& kSecAttrAccessGroup
) – seems to be working well, haven't found any issues (will update if there are any)
Edit: opened #144
Can't believe it's now 2024.
I don't know much about iOS, but it works without issues when I only have to store key-string pairs.
Currently,
KeychainSettings
is considered experimental because I want to be cautious about security-related APIs and I've had very little feedback. Please report this ticket if it is or isn't working for you so I can get a sense of when it's ready to be marked stable.