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

I'd like to add my name to this issue. I often keep several dozen tabs open, so I can't update Chrome every time a new version is available. It's a major pain to restart the browser. Having 1Password require the master password every few minutes is just as big of a pain. I'm also considering looking for a new solution if this can't be resolved. From the comments above, it seems there are other options that don't have this issue. I have the annual family plan and I don't want to change services, but this problem is going to force the issue.

Not ready to post in detail about this yet but just want to say I'm very interested in this discussion: how the 1Password Application PC/macOS, 1Password Chrome Extension, and Chrome/'Google Update' interact with each other and present challenges to efficient-use/workflow.

I'd like to add my voice to this as well -- there has to be a better way to handle this, while still maintaining security.

I also find this behavior very frustrating, but having looked into it I don't think there's much 1Password can do here without compromising security. Presuming it's even possible, end-running MacOS' code signature checks would be hacky and prone to vulnerabilities.

It seems clear that Chrome's method of overwriting the static (disk) copy of the code violates the expectations of MacOS' SecCode framework, so it really is on Google to conform to the platform on which Chrome is running. (FWIW it seems like writing a new Chrome to disk and only moving it into place when it's about to be run would do the trick, but it begs credulity to imagine the Chrome devs haven't thought of that; so there must be some non-obvious problem with it.)

It would be nice to have some confidence that Agile Bits are actively in touch with Google and actively pushing them to resolve this issue. Google is aware of, tracking, and implementing workarounds to https://bugs.chromium.org/p/chromium/issues/detail?id=1297588 bugs rooted in Chrome overwriting itself on disk while it's still running, but 1Password isn't in the list. There is one public Chrome https://bugs.chromium.org/p/chromium/issues/detail?id=622770 specific to 1Password, but it's 6 years old and hasn't had any activity in it for 3.5 years. Which gives the appearance that Agile Bits are resigned to it as intractable, when it can (and should) be fixed. Squeaky wheel…

This is really painful. Browser updates happen too often and I have to close all my tabs.

Same here, about to cancel my subscription. I have a rather long master password. Chrome extension makes me enter my pass ~10 times a day. If I cancel integration with desktop app, it asks constantly.

Any solid plans to address this issue?

Same, this is super annoying

Hey @kirbiyik, are you asked to enter your Account Password even when there are no updates needed in Chrome? If so, then it might be a totally different issue. Let me know more about what's happening and I will do my best to help.

This is very annoying and I think part of the ultimate solution here is the same thing that will help on other platforms: Make the browser extension fully capable on its own.

The annoyance of 1Password locking at every turn is something that happens:
* When Chrome is ready to update
* When using a browser that 1Password doesn't know about like Ghost
* When using a platform that doesn't have a native app, like Chromebooks (ChromeOS)
* When using iOS, though fortunately Touch/Face ID reliably unlocks 1Password

In all of these cases, we could lower the annoyance-factor to zero if the 1Password browser extension was fully capable on its own, able to set the same Security preferences as the Mac app.

Hey @Joy_1P, I think it's connected. So in my case, if there is a waiting update it asks password almost every time. Likewise I have a lot of tabs open, only restart my browser once in a few weeks. Is there a workaround to this?