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

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!

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?

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.

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.

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