You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
I am using SwiftKeychainWrapper in my project. It's working most of the time without any issue. But in very few cases My app is unable to access KeyChain. And after that, no matter what, user restarting app, keyChain is always return nil.
Pod version: 3.4.0
Implementation logic:
On app very first launch (Fresh Install case) (Not update or upgrade case), I remove old keyChain Data Using: KeychainWrapper.standard.removeAllKeys(), thus my app can generate new value and use them.
And other cases I always uses KeychainWrapper.standard.set(.... && KeychainWrapper.standard.string(.... apis to get and set values for my app.
Is there any issue for accessing KeychainWrapper.standard just after removing All old values?
Or this is some king of bug?
The text was updated successfully, but these errors were encountered:
anjananoup
changed the title
[Very Rare] Key Chain is inaccessible on app Reinstall case
[Very Rare] Key Chain is inaccessible/return nil
Mar 19, 2020
I am having the same issue.
For just one of our clients (around 2000), KeychainWrapper.standard.string(... always returns nil. It is working fine for all other clients.
I am using SwiftKeychainWrapper in my project. It's working most of the time without any issue. But in very few cases My app is unable to access KeyChain. And after that, no matter what, user restarting app, keyChain is always return
nil
.Pod version:
3.4.0
Implementation logic:
On app very first launch (Fresh Install case) (Not update or upgrade case), I remove old keyChain Data Using:
KeychainWrapper.standard.removeAllKeys()
, thus my app can generate new value and use them.And other cases I always uses
KeychainWrapper.standard.set(....
&&KeychainWrapper.standard.string(....
apis to get and set values for my app.Is there any issue for accessing
KeychainWrapper.standard
just after removing All old values?Or this is some king of bug?
The text was updated successfully, but these errors were encountered: