Retrieving Secrets in 5.0.0

[mehroozkhan]

Hi ,

I update the library, but now I can't access secret, can you please help,

I use to get secret like this :

let secret = KeychainStorage<Secret>().all().first

this is to check if user is already login.

but with the update its giving me an error: can't find keychainstorage in scope

[sbertix]

Hey @mehroozkhan,

You can either import ComposableStorageCrypto or use the new authentication flow.

let secret = try? Authenticator.keychain.secrets.get().first

Check out the Followers example to see more use cases.

[biox86]

Hello guys, something strange related to the login process happened to me. Thought about writing about it in here cause the subject is pretty much the same.

The problem happened just on the simulator trying to login with Authenticator.keychain ( logging in with Authenticator.userDefaults worked perfectly ).

I was constantly getting failure from the authenticator with Swiftchain.Keychain.Error.status(-25303).

After resetting the device the problem disappeared completely and started working correctly.

The snippet of the authenticator is pretty much a basic one:
DispatchQueue.main.asyncAfter(deadline: .now()) {
Authenticator.keychain
.visual(filling: self.view)
.authenticate()
.receive(on: RunLoop.main)
.sink(receiveCompletion: { print($0); self.dismiss(animated: true, completion: nil) },
receiveValue: completion)
.store(in: &self.bin)
}

What do you think could have caused this problem?
Could it be related to something saved in the keychain with the old KeychainStorage class from ver 4.x that could have caused some conflicts?
Or maybe could just be the keychain that is not working well on the simulator?
I know it doesn't really feel like a real bug, but maybe I'm just missing something about keychain logic.

EDIT:
My analysis was wrong. The problem persists and it happens on bot sim and device.

The first login works correctly and it saves the secret inside the keychain, but if I try to login again and re-save it in the keychain the authenticator always responds with that error.

[sbertix]

Hey @biox86,

It seems like it might be the same exception that's already been patched.
Make sure you update your SPM dependencies and ComposableRequest is on 5.0.9. If it still persists afterwards, please open an issue with some more info 💪