-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FXKeychain failed to retrieve data for key 'token', error: -34018 #31
Comments
I'm having the same issue |
me too FXKeychain failed to retrieve data for key |
+1 |
Apple are aware of it... https://forums.developer.apple.com/thread/4743#14441
|
Is it only when accessing the keychain right at launch? I'm getting this well after the app launch... |
Having the same issue. Is there a solution to this problem? Thanks |
Having the same issue and the workaround that Apple provided with the delay is not working for me either. Hope there will be a fix in a new iOS version soon though. |
Having the same issue only when running in debug mode with Xcode with the device connected to the debugger. |
Having the same issue only when running in debug mode with Xcode/AppCode with the device connected to the debugger... |
Same issue here in iOS 9.2.1. When device is not connected to the debugger it works ok for me. |
Same issue with iOS 10 and iPhone 7 simulator... |
@bimusiek and all others getting this issue: If you're getting this issue now, it's likely because iOS 10 now requires a new entitlement for keychain usage. Here's the fix: Go to your project target and under capabilities add Keychain Sharing to your app. It immediately resolved my issues. |
@jboulter11 Yes, you are right. I forgot to reply here after I found the solution. Confirmed, you have to enable Keychain Sharing, however for me this is not really the solution for people that do not want to share Keychain :) However, the fault is at Apple side. |
This error comes sometimes while reading data from shared keychain by multiple apps. Can somebody explain what's causing this?
The text was updated successfully, but these errors were encountered: