1Password chrome extension keeps getting locked because an update is available

I'm so sorry I missed your last message @laffingleigh, did you get a response over email from the team?

The Support ID number should look something like: #ABC-12345-321

@steph_giles Yes, I got many responses, but most of them hadn’t read through this email chain. I finally had someone read through the email chain and really seemed to understand. We left off with the notion that this is indeed a problem and there is currently no solution. Bummer.

I do not see any support ID number in any of the emails.

Can this please be fixed (at least in the short term) by letting us disable code signature validation for selected browsers? We finally have the ability to select trusted browsers, so this really isn't a huge leap.

I might try disabling chrome-auto updates because this behavior is so frustrating.

Hey 1Password.. Chrome has moved to weekly updates:

https://security.googleblog.com/2023/08/an-update-on-chrome-security-updates.html

and I'm at wits end with 1Password failing.

I certainly can't try to get my family to start using our teams account when the passwords which were "just there" in their chrome profile don't go missing.

I never have cared what security benefit there is from having the extension validate the browser.. now that the browser is pretty much always considered invalid, we really need a better workflow here.

YES! This is my one and only deep, deep frustration with 1password. Restarting Chrome is not a trivial exercise, it's equivalent to restart my entire computer (as most of my work is browser-based). I can't even do it while in meetings, because our meetings are also browser-based. It basically makes 1password incredibly painful to use, for several hours/days each time, every 1-2 weeks. This is a UX disaster!

And the only reason I cannot, in good conscience, recommend 1password to my colleages.

I made an account on these fora just to :+1: this. There are plenty of times I don't have the bandwidth to reload every tab on chrome and can't restart it, so 1pass becomes unusable.

Are there any useful workarounds? Does disabling chrome auto-updates work?

Adding to this thread. I read the thread and understand what causes this, but its really annoying and +1'ing my feedback for a fix or change. Not a great experience. Thank you

This thread only (and there are many more) started in Nov 2021. So I just cancelled my subscription because of this long frustration. Been using 1Pass for over 10 years, good job team

+1 here as well. It's so frustrating with the pace that Chrome issues updates.

It's not even the end of October and so far this month we've had 118.0.5993.96, 118.0.5993.88, 118.0.5993.70, 117.0.5938.149 and yesterday 118.0.5993.117. I can see why you would want to ensure that Chrome is up to date to allow 1Password to unlock, but please consider introducing some kind of grace period such as that within Chrome itself where the status in the top right hand corner goes green to gently let you know that there's an update available, followed by orange if you ignore it for a day or two until finally becoming red and angry.
As others have already said in this thread, restarting the whole browser just to get 1Password to integrate properly is not a viable option in this day and age. For a lot of us, the browser is where we spend 99% of our working computer time and as silly as it sounds, restarting the browser usually results in a break in productivity and flow.