I'm happy to help.

Please note that 1Password Classic, the old extension that was responsible for saving and filling logins in the browser, will stop working soon. You can read more here: The 1Password classic extension will stop working soon

Our modern extension is being actively worked on and will be our focus going forward.

-Dave

Yeah, thanks.

Thank you for reporting the issue. Our developers have released fixes for both 1Password 7 and 1Password 8:

We’ve implemented a change to make sure the connection between the 1Password app and browser extension continues to work properly in the upcoming versions of Microsoft Edge, Chrome, and other Chromium-based browsers.

Please update to the latest versions to take advantage of the fix.

-Dave

David Tears,

As a company focused on security, you fail to properly test your extensions against the upcoming releases of Chrome and then balk when users do your testing for you. Your extensions are 100% broken for 1Password 7.x and 8.x when used in Chrome 113.

You also do non-nonsensical tamper checks like this one:
opw_app::managers::browser_manager:52 > failed to validate browser. Error: opw-app\src\nmh.rs:133 untrusted chromium browser
Native Hosts should avoid any reliance on the particular process tree of their launch context, as any number of things (including this change) could cause such checks to become flaky.

And you can't even properly configure your own web servers:
https://1password.com/downloads/?stupidbug

The path forward is to use another password manager that is backed by reputable open source development that secures a local vault -- not 'fake security'.

1Password Version: 7,8
Extension Version: all
OS Version: any
Browser:_ Chrome 113

As a company focused on security, you fail to properly test your extensions against the upcoming releases of Chrome and then balk when users do your testing for you. Your extensions are 100% broken for 1Password 7.x and 8.x when used in Chrome 113.

You also do non-sensical tamper checks like this one:
opw_app::managers::browser_manager:52 > failed to validate browser. Error: opw-app\src\nmh.rs:133 untrusted chromium browser
Native Hosts should avoid any reliance on the particular process tree of their launch context, as any number of things (including this change) could cause such checks to become flaky.

And you can't even properly configure your own web servers:
https://1password.com/downloads/?stupidbug

The path forward is to use another password manager that is backed by reputable open source development that secures a local vault -- not 'fake security'.

1Password Version: 7,8
Extension Version: all
OS Version: all
Browser:_ Chrome 113

As a company focused on security, you fail to properly test your extensions against the upcoming releases of Chrome and then balk when users do your testing for you. Your extensions are 100% broken for 1Password 7.x and 8.x when used in Chrome 113.

You also do non-sensical tamper checks like this one:
opw_app::managers::browser_manager:52 > failed to validate browser. Error: opw-app\src\nmh.rs:133 untrusted chromium browser
Native Hosts should avoid any reliance on the particular process tree of their launch context, as any number of things (including this change) could cause such checks to become flaky.

And you can't even properly configure your own web servers:
https://1password.com/downloads/?stupidbug

The path forward is to use another password manager that is backed by security running a local vault -- not 'fake security'.

1Password Version: 7-8
Extension Version: All
OS Version: All
Browser:_ Chrome

Not acceptable. As a company focused on security, you fail to properly test your extensions against the upcoming releases of Chrome and then balk when users do your testing for you. Your extensions are 100% broken for 1Password 7.x and 8.x when used in Chrome 113.

You also do non-sensical tamper checks like this one:
opw_app::managers::browser_manager:52 > failed to validate browser. Error: opw-app\src\nmh.rs:133 untrusted chromium browser
Native Hosts should avoid any reliance on the particular process tree of their launch context, as any number of things (including this change) could cause such checks to become flaky.

And you can't even properly configure your own web servers:
https://1password.com/downloads/?stupidbug

The path forward is to use another password manager that is backed by security running locally, not fake security.

Hello! 👋

1Password Classic was last updated in 2019. It was built on older technologies and will not be compatible with future updates to web browsers. Our modern extension, 1Password in the browser, is in active development: https://support.1password.com/getting-started-browser/

The modern extension requires a membership and doesn't work with older standalone vaults. I recommend sending an email to our support team at support+tradein@1password.com so that they can look at how you're currently using 1Password and advise on the best path forward.

-Dave

Maybe the Chrome team will fix on their end. When Manifest V2 extensions are denied in Chrome at some point, problems will re-emerge. It's just a pity to have to migrate all password data to another product when I already paid. No need for diagnostic data from me as you have a workflow and can check what you say you don't support anymore :)