Chrome Version 100.0.4896.30 (Official Build) beta won't verify

I can confirm this. Same issue here. 1P keeps assuming that Chrome has an update available (which, it doesn't). Hence the extension won't auto-unlock or integrate with 1P Desktop.

Yes, excactly

Hey @MrPunkin and @cryptochrome:

Thanks for reporting this! We're actively aware of this (Chrome's code signing certificate recently changed in beta / canary releases) and are working to resolve this with an update to 1Password 7 for Mac. In the meantime, 1Password should still be able to communicate with Chrome stable releases. Let me know how you get on with that!

Jack

Thanks @Jack_P_1P. I work in web-dev and won't be rolling back to Stable Chrome anytime soon. Here's hoping the beta channel of either 1Password 7 or the Chrome extension gets updated soon and there's minimal copying/pasting of logins. Thanks for the update though, glad to know the team is aware of it.

If it's just a changed certificate, it's probably an easy fix. For those of you who don't want to roll back to Chrome stable: You can still unlock 1P in the browser manually (enter master phrase) and then it works without issues. Might want to disable automatic logout in the extension settings if you don't want to have to keep unlocking it every couple of minutes.

@cryptochrome According to the beta release log for Chrome it looks like they changed the signing process for user profiles in the March 10th release. I think the 1Password team probably has a bit of work to do to match the new system.

Hey @MrPunkin:

Thanks for following up! Keep an eye out for updates to 1Password for Mac, as that is where the fix will be made! 😀

Jack

Hey @MrPunkin / @cryptochrome:

Thanks for your patience on this! 1Password for Mac version 7.9.3 is now available, which includes the fix for the updated certificate. Check for updates and let me know how it goes for you both: How to keep 1Password up to date

Jack

Hey @""Jack.P_1P" - I can confirm the integration between 1P Desktop and 1P Browser is working again. Thanks for the quick fix!

Yep I can confirm this is working again. Thank you!