TouchID timeouts and Extension position - bugs? [Answers in post #11]

2»

Comments

  • digitaldog
    digitaldog
    Community Member

    Thanks Megan, I have exactly those settings expect I had Request Fingerprint After> 1 hour. I've updated to your settings. Let me go a few hours and see if indeed I can get into the product with just the TouchID. Thanks!

  • Megan
    Megan
    1Password Alumni

    Hi @digitaldog,

    I've got my fingers crossed that things work out for you exactly as you expect! You know where to find us if you have any further questions though. ;)

  • digitaldog
    digitaldog
    Community Member

    Sorry to say, a few hours later, I'm still asked to enter the master passsword, not via TouchID. Happy to provide any additional info, logs of the like if your product creates them that would pin down the problem. I'm assuming I'm not the only one with the new iPhone, iOS8 having this issue?

  • dsjr2006
    dsjr2006
    Community Member

    Megan those settings should give the results you describe, but I'm still having to enter my password multiple times per day despite not turning off my phone, etc.

  • Ben
    Ben

    Hi @digitaldog‌ And @dsjr2006‌

    Have you both tried toggling Settings > Advanced > Use iOS Keychain OFF and then back ON?

    Thanks.

  • digitaldog
    digitaldog
    Community Member

    Have you both tried toggling Settings > Advanced > Use iOS Keychain OFF and then back ON?

    Yes, several times. But I'm testing this again today after the 8.0.2 update so stay tuned. I want to give the app a few hours.

  • Ben
    Ben

    Okay, please let us know how it turns out, @digitaldog‌

  • digitaldog
    digitaldog
    Community Member

    Not working. I've sent myself the log file so I can send to you guys an email with it, as instructed in another forum post about providing this data.

  • digitaldog
    digitaldog
    Community Member

    OK, today it seems I can indeed go longer than 1 hour with TouchID, don’t know what changed but let's go a few days, I'll do more testing and get back to you.

  • Ben
    Ben

    Please keep us updated, @digitaldog.

  • digitaldog
    digitaldog
    Community Member

    It has been working now over the weekend! Don't know what changed but I'm happy to say I can go hours (days) and TouchID works.

  • Megan
    Megan
    1Password Alumni

    Hi @digitaldog,

    I'm so glad to hear that things seem to be working now! I hope things continue to behave, but you know where to find us if you hit any further snags. :)

  • Patrick Cates
    Patrick Cates
    Community Member

    Hi there,

    I've been having the same problem with the Touch ID timing out after, in my case, around a day. I have configured the Security settings just as you showed above (except I have a 1-minute fingerprint request set instead of 2 minutes, which I can't think would make a difference, although I'm going to set it to 2 now just to be sure). I have also tried toggling off the "Use iOS keychain" setting in Advanced and turning it back on again. I did this yesterday and when I went into 1Password on my phone this morning, I was prompted for my master password. I have not restarted the phone since. So something is afoot with pulling the credentials from the keychain. I looked in the diagnostic file and here are the lines that seem to indicate when the Touch ID works as expected:

    Wed Oct  1 11:14:36 2014| 500103 [LOCKSERVICE:0x178078000:<OPLockService: 0x1780910d0>] S loadLocalAuthenticationFramework | Loading LocalAuthentication.framework
Wed Oct  1 11:14:36 2014| 500103 [LOCKSERVICE:0x178078000:<OPLockService: 0x1780910d0>] S restoreState | Lock mode changed (2): QuickUnlock
Wed Oct  1 11:14:36 2014| 500103 [LOCKSERVICE:0x178078000:<OPLockService: 0x1780910d0>] S storeMasterPasswordInSystemKeychain | 
Wed Oct  1 11:14:37 2014| 500103 [APP:0x178078000:<OPAppDelegate_iPhone: 0``x1781029a0>] S application:performFetchWithCompletionHandler: | Starting background fetch...
Wed Oct  1 11:14:37 2014| 500103 [REPLICATOR:0x178078000:<OPAgileKeychainReplicator: 0x17009a5e0>] S run | Keychain replicator started

    However, here are the lines (I think) that correspond to the unexpected request for the master password:

    Thu Oct  2 10:20:18 2014| 500103 [LOCKSERVICE:0x17007d2c0:<OPLockService: 0x17009fb30>] S loadLocalAuthenticationFramework | Loading LocalAuthentication.framework
Thu Oct  2 10:20:18 2014| 500103 [LOCKSERVICE:0x17007d2c0:<OPLockService: 0x17009fb30>] S clearMasterPasswordFromSystemKeychain | 
Thu Oct  2 10:20:18 2014| 500103 [LOCKSERVICE:0x17007d2c0:<OPLockService: 0x17009fb30>] S setAppLockMode: | Lock mode changed (3): 'MasterPassword'
Thu Oct  2 10:20:18 2014| 500103 [UTILS:0x17007d2c0:<AGUserKeychain: 0x178420840>] E setData:forAccount: | Failed to store 'lock-service' keychain data for account 'state': -25308
Thu Oct  2 10:20:20 2014| 500103 [APP:0x17007d2c0:<OPAppDelegate_iPhone: 0x17011ac10>] S application:performFetchWithCompletionHandler: | Starting background fetch...
Thu Oct  2 10:20:20 2014| 500103 [REPLICATOR:0x17007d2c0:<OPAgileKeychainReplicator: 0x17028e1f0>] S run | Keychain replicator started

    It seems that the app is having a problem accessing the keychain data periodically (which I'm guessing corresponds to the master password request). Here's the line that looks fishy:

    Thu Oct 2 10:20:18 2014| 500103 [UTILS:0x17007d2c0:<AGUserKeychain: 0x178420840>] E setData:forAccount: | Failed to store 'lock-service' keychain data for account 'state': -25308

    Could it be that some other app is trying to access the keychain at the same time or something like that?

    Anyway, hopefully the above is of some use. This is definitely still an issue.

    Thanks,

    Patrick

  • Megan
    Megan
    1Password Alumni

    Hi Patrick Cates,

    Thanks for providing the detailed report here! Our developers are looking into the TouchID issue, and you should see an update soon that has this all behaving a lot more reliably.

    In the meantime, some users have had success with disabling background app refresh for 1Password in Settings.app. Please give that a try and let me know how things work!

    In any case, we'll do what we can to have this update out to you all soon!

This discussion has been closed.