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

Hey @pastelsky ,

This happens because the extension is integrated with your 1Password desktop app. The integration breaks when the browser has a pending update because its code signature is invalidated. If something else alters your browser's files and changes the code signature, this message might show up again.

If you'd like to keep working with the extension even when there's a pending update or with an invalid code signature of the browser, right-click the extension's icon -> Settings -> Turn off the "Integrate with 1Password app" option there.

Thanks @ag_yaron . I understand that, but given that evergreen browsers update often, its a little annoying. What are the consequences of —
Settings -> Turn off the "Integrate with 1Password app"
I guess this means that I can't use some other features?

That's correct.
Turning off integration will separate the extension from the desktop app so it will run in standalone mode, meaning you will have to unlock it separately from the desktop app, and unlocking with Touch ID/Windows Hello will not be possible.

I'll forward this to the team and see if there's anything else we can do to make things easier though :chuffed:

Turning off the integration unfortunately makes the integration worse, and I need to type in my master password more frequently then ever. This basically makes 1Password unusable on my primary browser — Chrome Canary.
That's a little unfortunate considering other password managers I've tried — NordPass and Lastpass seem to not have this problem. I wish there was a fix for this.

@pastelsky

You're right, this is not ideal. However for 1Password to maintain a secure connection to your desktop app, it needs to be able to validate the code signature of the browser. Without this, integration will not work. I'll be happy to pass along your feedback to our development team, hopefully we can improve things here in the future!

However for 1Password to maintain a secure connection to your desktop app, it needs to be able to validate the code signature of the browser

That does make sense, however, it's something that I would expect to happen when I actually hit update on Chrome. Chrome dev/beta / canary download updates quite frequently in the background — may be several times a week, however, I may only hit update less often.

Currently, 1Pass invalidates the session as soon as a background upgrade is downloaded.

@pastelsky

Currently, 1Pass invalidates the session as soon as a background upgrade is downloaded.

We only invalidate after we attempt a reconnection with the desktop app. But I can see how the two might coincide if the browser updates multiple times in a single day/session. As Yaron suggested, disabling integration might be the best approach for your case in the meantime. We'll continue to work with our development team to see if we can find ways to improve the experience here. Apologies for the disruption.

Given how often Chrome is being updated, this headache is causing me to seriously considering going back to using LastPass.

Same - this is a really annoying behaviour even with a standard Chrome installation - Updates are too frequent. I'm considering switching to another app too.

Is there no way to have 1Password be aware of the code signature of both the old and new versions of the browser? This security feature makes using 1Password + Chrome + Touch ID really frustrating given how often Chrome updates. Turning off the desktop integration is not a solution because then I lose the Touch ID support. Hope you can come up with a user-friendly solution for this one that doesn't sacrifice security!