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

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…