Touch ID in 1Password 5

Jeff Shiner
edited October 2014 in iOS

There have been a number of reports of the Master Password appearing when Touch ID (or PIN Code) is expected. Here are a couple of reasons why that might be happening to you:

Settings

We have found that the settings themselves can be confusing, in particular, the fact that there are two separate Auto-Lock settings. There is one for the Master Password and a second for Touch ID / PIN Code. Both work together to determine what lock screen you see.

For example, let's say you have the Master Password set to 1 hour and Touch ID set to 2 minutes. This means that 1Password will Auto-Lock with Touch ID after 2 minutes of inactivity, and Auto-Lock with the Master Password after 1 hour of inactivity.

It is important to note that the Master Password will always take precendence. If you have both the Master Password and Touch ID set to 10 minutes you will never see Touch ID appear as the Master Password will take over.

We are simplifying the Security settings in an upcoming release and will have only a single Auto-Lock setting. That setting will use the current lock method you choose. If you choose to use Touch ID then it will Auto-Lock to Touch ID, if you choose to use the Master Password it will Auto-Lock to the Master Password.

1Password Extension

We have also found an issue that is affecting the reliability of Touch ID (or PIN Code).

We have found an issue where the 1Password Extension is not properly resetting the Master Password Auto-Lock timer. This means that 1Password continues to believe that the Master Password Auto-Lock timeout has expired, and requires the Master Password on each launch of the extension.

Unlocking the main 1Password app will properly reset the timer, and allow you to unlock 1Password or the 1Password extension with Touch ID until the Master Password Auto-Lock timeout expires again.

This issue has been fixed and will be available in the next update.

Touch ID FAQ

If you want to learn more, you can read our Touch ID FAQ.

This discussion has been closed.