Skip to main content
LarryMcJ
December 2, 2022
Question

TouchID requires password too often

  • December 2, 2022
  • 45 replies
  • 3064 views

I realize there are several discussions about this, but in order to provide something definitive, I did an experiment, keeping track of all results. I ensured 1Password was configured to require a password for TouchID every 30 days (screenshot below). In a single 48-hour period, using 1Password on macOS (Ventura v13.0.1), I used AutoFill a total of 50 times. Out of those 50 times, 1Password required my actual password (not TouchID) 10 times. If this is a bug and expected behavior...I'm perfectly fine with it. But if it's not supposed to occur, can someone explain why it does? Having to type in a password this often defeats the purpose of TouchID. Thanks.


1Password Version: 8.9.8
Extension Version: 2.4.1
OS Version: macOS 13.0.1
Browser:_ Safari

45 replies

December 12, 2022

FWIW, upgrading to v8.9.10 seems to have fixed this

Not for me. I'm on 8.9.10. I will say that my install seems buggy in general though.

LarryMcJ
LarryMcJAuthor
December 12, 2022

More folks than not don't have this issue, though I certainly know it's real. If it returns for me, I'll do what one of the Agile folks recommended, and rip it completely off my Mac and do a complete reinstall, preferences and all.

andrew_l_1P
1Password Employee
December 13, 2022

@LarryMcJ,

Glad to hear an update resolved things on your end, thanks for updating folks here on the forum. Hopefully you'll never have to do a full re-install but certainly a troubleshooting step to keep in your back pocket. 🙂

@philb74 and @whackit,

If you folks are still experiencing this on the latest versions of 1Password and MacOS, I'd like to ask you to create a diagnostics report from your Mac:

Attach the diagnostics to an email message addressed to support+forum@1password.com along with your forum username and a link to this thread. We'll connect your conversations and take a look under the hood to see what's going on.

If you'd prefer to try a fresh installation first, you can find instructions on our website here: How to uninstall 1Password

Thanks for your patience, looking forward to getting this resolved for you both. 😊

LarryMcJ
LarryMcJAuthor
December 13, 2022

Well...I may have spoken too soon, as it happened twice this morning. Unfortunately, it will just have to wait as I'm slammed until Friday.

December 28, 2022

I have some additional infos about my current setup, which I think could be related to the problem.

  • I'm always using an external monitor and have my Mac Book Pro's lid closed. Touch ID is disabled in that case, but Apple Watch is still working.
  • If unlock with Apple Watch is not working, I wait for some time (can't say exactly how long it takes) and unlock with Apple Watch works again.
  • It also works most of the time when I open the lid of my Mac Book Pro when this issue occurs. Touch ID gets activated an I can unlock with Touch ID, even if Apple Watch is not working.

Maybe someone else have similar experiences?

Cheers, Phil

LarryMcJ
LarryMcJAuthor
December 28, 2022

Hmmm…I have an M2 MacBook Air (display closed) and an Apple Studio Display. But I rarely have my AW on when I’m in my office.

LarryMcJ
LarryMcJAuthor
January 6, 2023

FWIW, this is still an intermittent problem for me - using v8.9.11 (80911019) on an M2 MBP. Some days I'll use 1Password 10 times and it invokes TouchID each time. Other days, it requires a password several times in succession. This is the same pattern my wife experiences on her Mac mini so I don't think it's limited to my installation. Something definitely still wrong.

January 7, 2023

@LarryMcJ do you use an external keyboard without touch sensor? Support told me, they are looking into an open issue with this setup.

LarryMcJ
LarryMcJAuthor
January 7, 2023

No. I use an M1 MBA, Apple Magic Keyboard (with TouchID) and an Apple Studio Display.

My wife uses the latest iMac with an Apple Magic Keyboard (with TouchID).

LarryMcJ
LarryMcJAuthor
January 27, 2023

This is definitely still a thing. Any hope of it being resolved somewhere in the future?