2

I've been using KeychainItemWrapper just fine. But since I've updated my phone to iOS 9, it doesn't store the sessionID for some reason.

    + (BOOL)createKeychainValue:(NSString *)value forIdentifier:(NSString *)identifier
{

    NSMutableDictionary *dictionary = [self setupSearchDirectoryForIdentifier:identifier];
    NSData *valueData = [value dataUsingEncoding:NSUTF8StringEncoding];
    [dictionary setObject:valueData forKey:(__bridge id)kSecValueData];

    // Protect the keychain entry so it's only valid when the device is unlocked at least once.
    [dictionary setObject:(__bridge id)kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly forKey:(__bridge id)kSecAttrAccessible];

    // **THIS LINE OF CODE RETURNS -34108**
    OSStatus status = SecItemAdd((__bridge CFDictionaryRef)dictionary, NULL);

    // If the addition was successful, return. Otherwise, attempt to update existing key or quit (return NO).
    if (status == errSecSuccess) {
        return YES;
    } else if (status == errSecDuplicateItem){
        return [self updateKeychainValue:value forIdentifier:identifier];
    } else {
        return NO; **The call returns here...**
    }
}

Anybody know whats going on?

EDIT

Weirdest thing: it only happens from time to time and always in debug mode.

EDIT2

As this only occurs in debug mode, there are two work arounds that I usually do depending on the type of variable: - Always keep the last valid variable loaded from the keychain locally (for instance a sessionID) and use it as a backup when in debug mode - Ignore invalid value(s) if possible when in debug (in this case I would add an additional control variable to allow/disallow these invalid value(s))

(use #ifdef DEBUG to check if you're in debug mode)

4

1 回答 1

0

根据 Apple 的说法,目前没有解决方案。 https://forums.developer.apple.com/thread/4743

于 2015-09-05T20:20:05.007 回答