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
There is an issue using shared keychain items only in Yosemite using iOS 8 simulators. It appears that the kSecAttrAccessGroup is now needed in this specific configuration. Keychain calls that would previously fail when including the kSecAttrAccessGroup key with an error of -25243 are now successful. Further, the shared keychain does not appear to be globally available to the simulator requiring the kSecAttrAccessGroup key to be used. I simply commented out the simulator check in dataForKey: and setObject:forKey:
Interestingly, commenting out these checks also prevented a deadlock situation where the dataForKey: method would block in a semaphore_wait when calling out to SecItemCopyMatching on this line: OSStatus status = SecItemCopyMatching((__bridge CFDictionaryRef)query, (CFTypeRef *)&data);
I experienced this in the iOS 8 simulator running in Yosemite 10.10.1 (14B25) w/Xcode 6.1.1 (6A2008a)
@ekurutepe Unfortunately this fix only works for the iOS 8 simulator on Yosemite. Commenting out the simulator exceptions causes the shared keychain access to fail on iOS 7 simulators on Yosemite and both iOS 7 & 8 simulators on Mavericks. Therefore, I don't see a reasonable resolution in code. Apple needs to make a fix.
There is an issue using shared keychain items only in Yosemite using iOS 8 simulators. It appears that the kSecAttrAccessGroup is now needed in this specific configuration. Keychain calls that would previously fail when including the kSecAttrAccessGroup key with an error of -25243 are now successful. Further, the shared keychain does not appear to be globally available to the simulator requiring the kSecAttrAccessGroup key to be used. I simply commented out the simulator check in dataForKey: and setObject:forKey:
I haven't figured out any other way around this issue yet.
Update: I'm using OS X Yosemite v10.10.1 (14B25) and Xcode 6.1 (6A1052d)
The text was updated successfully, but these errors were encountered: