Quick unlock not available in b2 [Confirmed, we're looking into it, might be an iOS 8 bug]

foad
foad
Community Member
edited July 2014 in iOS

Hey folks.

I'm not seeing an option for a passcode unlock in Settings. I have to always enter the Master password. I'd rather not extend the time for requiring a password for security reasons but having to reenter my convoluted master password is cumbersome.

Is anyone else seeing this?

Comments

  • patte
    patte
    Community Member

    Yep. Was just going to post this, too. When trying to enable Quick Unlock the toggle/pill immediately switches back to "off".

  • foad
    foad
    Community Member

    I don't even have the toggle.

  • myckmack
    myckmack
    Community Member

    Same as patte :-(

  • joetomasone
    joetomasone
    Community Member

    No toggle here either.

  • lem3ssie
    lem3ssie
    Community Member

    Me too, nothing to set a pin code up, and can't deactivate master password

  • tommyang
    tommyang
    Community Member

    When trying to enable Quick Unlock the toggle/pill immediately switches back to "off".

    Same here. Console Msg:

    Jul  2 19:16:55 Tommys-iPad-Air kernel[0] <Notice>: AppleKeyStore: operation failed (pid: 1156 sel: 43 ret: e00002e2)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Critical>:  SecDbItemCopyEncryptedData ks_encrypt_data (db): failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  SecDbItemInsertOrReplace INSERT failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  securityd_xpc_dictionary_handler 1PasswordBeta[1239] add The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Error>:  SecOSStatusWith error:[-25308] The operation couldn’t be completed. (OSStatus error -25308 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.))
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Warning>: Failed to store 'lock-service' keychain data for account 'up': -25308
    Jul  2 19:16:55 Tommys-iPad-Air kernel[0] <Notice>: AppleKeyStore: operation failed (pid: 1156 sel: 43 ret: e00002e2)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Critical>:  SecDbItemCopyEncryptedData ks_encrypt_data (db): failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  SecDbItemInsertOrReplace INSERT failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  securityd_xpc_dictionary_handler 1PasswordBeta[1239] add The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Error>:  SecOSStatusWith error:[-25308] The operation couldn’t be completed. (OSStatus error -25308 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.))
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Warning>: Failed to store 'lock-service' keychain data for account 'up': -25308
    
  • tommyang
    tommyang
    Community Member

    When trying to enable Quick Unlock the toggle/pill immediately switches back to "off".

    Same here. Console Msg:

    Jul  2 19:16:55 Tommys-iPad-Air kernel[0] <Notice>: AppleKeyStore: operation failed (pid: 1156 sel: 43 ret: e00002e2)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Critical>:  SecDbItemCopyEncryptedData ks_encrypt_data (db): failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  SecDbItemInsertOrReplace INSERT failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  securityd_xpc_dictionary_handler 1PasswordBeta[1239] add The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Error>:  SecOSStatusWith error:[-25308] The operation couldn’t be completed. (OSStatus error -25308 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.))
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Warning>: Failed to store 'lock-service' keychain data for account 'up': -25308
    Jul  2 19:16:55 Tommys-iPad-Air kernel[0] <Notice>: AppleKeyStore: operation failed (pid: 1156 sel: 43 ret: e00002e2)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Critical>:  SecDbItemCopyEncryptedData ks_encrypt_data (db): failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  SecDbItemInsertOrReplace INSERT failed: The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air securityd[1156] <Error>:  securityd_xpc_dictionary_handler 1PasswordBeta[1239] add The operation couldn’t be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.)
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Error>:  SecOSStatusWith error:[-25308] The operation couldn’t be completed. (OSStatus error -25308 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -25308 - ks_crypt_acl: e00002e2 failed to wrap item (class 12, bag: 0) Access to item attempted while keychain is locked.))
    Jul  2 19:16:55 Tommys-iPad-Air 1PasswordBeta[1239] <Warning>: Failed to store 'lock-service' keychain data for account 'up': -25308
    
  • 1Password now uses your device passcode as quick unlock. If you do not have a device passcode set up you will not see the Quick Unlock/Touch ID option in 1Password's Security settings.

    @tommyang‌, try disabling and then reenabling Touch ID on your device in Settings.app and see if that jogs 1Password into working.

  • patte
    patte
    Community Member

    My iPhone 5 doesn't have Touch ID, but passcode already activated. @MrRooni‌'s trick put my hopes up a bit, so I tried disabled and reenabled passcode in the iOS settings as an alternative. Result => Didn't work.

  • tommyang
    tommyang
    Community Member

    @MrRooni‌ It's actually working fine on my 5s, which has Touch ID. The symptom & those logs were on my iPad Air w/ device passcode enabled.

  • Hi guys,

    We believe there is a bug on iOS 8 regarding this issue on non-Touch ID devices and have filed a bug report with Apple. Hopefully, we'll have this fixed fairly soon.

This discussion has been closed.