Evgenii Neumerzhitckii

This was probably fixed by [this pull request](https://github.com/evgenyneu/keychain-swift/pull/68).

@RamblinWreck77, @MouldiGABSI, thanks for reporting. There was a multithreading [issue](https://github.com/evgenyneu/keychain-swift/pull/68) fixed since version 10 of the library. Make sure you are at version 10 at least.

Thanks for the pull request, but I can not accept it, unfortunately. I intended keychain-swift to be a pure Swift library, and try to avoid any references to objective-C. For...

I'm sorry about that. I hope you find a good objective-c friendly alternative. :)

Thank you for reporting the bug, @jhoughjr. I have just reproduced it, it does not clear the keychain items on OS X. I think it works on iOS because we...

Hi, thanks for reporting. This could be related to #15. Sometimes the Keychain returns nil, there is a potential workaround in #78.

Thanks, @RamblinWreck77. I can see that the the [accepted answer](https://stackoverflow.com/a/10583042/297131) suggests using `kSecAttrAccessibleAlways`: ``` keychain.set("Hello", forKey: "my key", withAccess: .accessibleAlways) ``` However, [another answer](https://stackoverflow.com/a/24642665/297131) recommends `kSecAttrAccessibleAfterFirstUnlock` setting instead for background...

@RamblinWreck77, no idea to be honest. I could not find anything specific about the password item type rather than this from the [docs](https://developer.apple.com/documentation/security/ksecclassgenericpassword): > kSecClassGenericPassword. > The value that indicates...

> claims his problem was a naming issue, where iOS was using the preferences of a previous keychain. Sorry, I don't understand what you mean. What is "previous keychain"? Is...

@dmavromatis, no there is no reliable solution unfortunately. It is a [mess](https://github.com/evgenyneu/keychain-swift/issues/15).