1Password 8 problems
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
Comments
-
Any suggestions on how to fix these issues other than downgrading to v7?
0 -
This is so frustrating. Even 1password 8 on iOS isn't working as well. It's doesn't always prompt to sign in when it needs to so I get no suggested username or password on login forms until manually open the 1password app to login. I can unlock it, then a minute later it won’t suggest usernames or password again. Ironically I had to unlock it twice to get it to sign in to this support forum. Would appreciate some help.
0 -
What the … and I can’t downgrade now back to the old app. Great!
0 -
Hi @jrdata2k:
1Password doesn't prompt to unlock automatically when unlocking your Mac. As for two 1Password accounts, 1Password 8 will only unlock 1Password accounts that share an account password. We generally recommend using the same account passwords for any 1Password accounts a single person has. Are you using the same account password for both 1Password accounts?
As for what you're experiencing with 1Password 8 on iOS, that definitely doesn't sound right. Is 1Password 8 enabled in the Settings app > Passwords > Password Options > Allow Filling From? Let me know.
Jack
0 -
It has always prompted to unlock using Touch ID when a password is needed. Now it doesn’t. I never get prompted to sign in and have to manually unlock every time. It’s gone from a seamless experience to… I need to login, why are there no username or password suggestions, ohh it’s locked itself again. I manually unlock by clicking on top menu icon, open 1password, finally get a prompt to unlock. I’m sorry but this process worked extremely well before, I would wake up my mac and if I needed to login to something I’d be prompted for Touch ID without having to go hunting around menus. After the update and now it’s frustratingly clunky with many more actions required to be able to sign in.
1password 7 always unlocked two accounts for me despite password differences. I can change this however and appreciate the suggestion but this is a difference in behaviour and a jarring experience after something has previously been working fine. I’ve “always” had separate password for each account and it’s been working fine for a long time until I upgraded. Anyway I’ll look into changing my password so both accounts are the same seeing as that sounds like a new requirement for things to work the way they did. If that doesn’t sound right I don’t know what to tell you, but it worked for me before the upgrade.
Auto-filling was turned off on iOS. I had this on previously, and I’m guessing this is because 1password 8 was a new app install, which as an app dev I find a strange choice rather than an update because things like this happen ie. user settings lost. Is the setting something your app can set if it was on for 1password 7? or you can detect the setting differs and streamline this by alerting the user on first use of the new app that it’s off? That might help with the transition issues.
Hopefully this fixes the iOS issues, and that the consolidated password helps account sign in on mac. Unsure about the added steps to unlock on mac however.
0 -
Hi @jrdata2k:
Thanks for following up. In that case, it sounds like 1Password in your browser might have having some trouble communicating with the 1Password desktop app. If you're experiencing this even after restarting your Mac, taking a closer look at the specific setup of 1Password on your Mac would be best. I'd like to ask you to create a diagnostics report and a console log from your Mac:
Sending Diagnostics Reports (Mac)
Save a console log for 1Password in your browser
Attach the diagnostics and console log to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread: https://1password.community/discussion/133524/1password-8-problems#latest
- Your forum username:
jrdata2k
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
0 -
So to confirm the iOS part, it is behaving much better and like it was before, I would never have worked this out without the suggestion, from a user perspective I wouldn’t have thought hey I need to setup the update the way it was before. But anyway thank you for that, it’s working the way it was.
0 -
Glad to hear that did it for iOS @jrdata2k. As for why 1Password 8 is a new app entirely, because 1Password 8 doesn't support standalone vaults, we wanted upgrading from 7 to 8 to be an explicit choice. We're hopeful that this is the last time we'll need to release a new app in the App Store. 😀
Jack
0 -
Re: diagnostics report, will do after trying to diagnose it some more. It’s late where I’m at but will get to it tomorrow, thanks.
0 -
Yup I was sure there would have been a good reason. I don’t quite understand what standalone vaults mean but hopefully you can smooth over the transition a little more by at least prompting the user to re-enable the auto-fill setting.
0 -
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.
0 -
@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.
0 -
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.
0
