Skip to main content
September 11, 2022
Question

1Password 8 problems

  • September 11, 2022
  • 13 replies
  • 1153 views

Hi there,

I seem to be getting a few problems that I used to get on older 1password 7 versions which had been fixed over the years. While it looks nicer, it's frustrating that it's taken backward steps on functionality.

I'm on Mac Monteray. I've updated to 1password 8, now when wake up my mac and sign in 1password never auto-signs in or prompts me to login using touch ID unless I click on the top right macOS menu icon which shows the 1password icon with a lock symbol and choose Open 1password.

I also get this old issue I used to have where I have two 1password accounts and only one gets logged in Chrome. I have to do this long winded process to unlock the second account every time where I click on the 1password extension icon > settings > my accounts > can see the second account is locked, then sign in to the account using master password. This was working fine in 1password 7.

Jason


1Password Version: 8.9.4
Extension Version: 2.3.7
OS Version: 12.5.1
Browser:_ Chrome

13 replies

September 13, 2022

So after re-enabling autofill on iOS, consolidating account passwords despite not needing that before, and I also ended up removing and reinstalling the chrome extension, restarting my mac, things seem like they're mostly back to the way they were working.

Still one odd little issue, if I start my mac up and 1pw is locked, if I load up a web page in chrome it shows a 1pw locked icon in a username or password field, I hit that and it prompts with a touch id sign in, I can authenticate that, but then when tapping back on the username or password field I get no auto-fill suggestions. If I immediately refresh the page the auto-fill works. It's like there's a case there where the auto-fill doesn't kick in or refresh.

Will report back any other issues I spot, but mostly back on track.

September 13, 2022

@Jack_P_1P I think the statement "recommend using the same account passwords" is the core anti-pattern 1Password as a company attempts to solve.

It's worth pointing out that @jrdata2k is correct in saying that the plugin failing with two accounts a regression that was solved, broken, solved again, and now is broken again. Here is a screenshot from my post in 2019.

Using the same passwords for two separate 1Password accounts is not a good solution, and should not be recommended because it is an unsafe practice. After all, many of us have separate 1Password accounts because we use one for work and one for personal life. Is it really a good idea to use the same password for highly sensitive work as my personal life? Certainly not.

This is a regression (now in its third manifestation) and should be addressed as such, instead of gaslighting it with dangerous UX recommendations.

September 14, 2022

It seems the issue I described in my previous comment above has improved after reinstalling the chrome extension.

^ but yes it sounds like this has been an on and off again issue. Not sure why the same issues come back in major updates. It's like there's some long standing upgrade bugs there that keep happening in major updates.