-
Notifications
You must be signed in to change notification settings - Fork 196
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
Fix keychain key bug #237
Fix keychain key bug #237
Conversation
This change fixes a bug where the String representation of these keys were supplied to the keychain query as opposed to the actual key names.
…nd watchOS as well
This check isn't needed since the enum case already has restricted availability.
Hi @olvrlrnz please take a look and help us to make sure that this change meets the need. Thanks! |
Examples/Example-macOS/Source/GTMAppAuthExampleViewController.m
Outdated
Show resolved
Hide resolved
Also update use of kSecAttrAccessible on macOS to only occur if also using kSecUseDataProtectionKeychain per Apple docs: https://developer.apple.com/documentation/security/ksecattraccessible\?language\=objc
The other existing methods either take an accessibility param or an optional param.
@olvrlrnz Sorry for bugging you again, but I made some changes since you last looked. Would you mind double checking for me? 🙏 |
Thanks for fixing this. Would it be possible to create a 4.0.1 release so we can update the package in Xcode? |
Absolutely. We need to figure out what version we call this. In any case, we will be making a new release to include a privacy manifest very shortly. I think that will come out in the next few weeks. Stay tuned for that, and sorry for the delay. |
This PR addresses a bug where the key attributes used to query the keychain were not being added correctly, and where therefore unused. The mistake was that the key names were assumed to match the static constants.
Fixes #236.