"Received <BrowserVerificationFailed> from the native core" since most recent Update

Well, isn't this a reminder from the past...
Well, I have, since originally submitting this issue, 3 years ago, actually changed laptops, and am running an up-to-date standalone version of the 1PW-App, again, with the mentioned and known downside, that my Chrome- Portable and Firefox-Portable (or rather, the 1Password-Extensions in those) can't access the Standalone Apps' passwords...).

Is there any plan of getting this fixed, still? (Either via whitelisting Extensions/Browsers via User-Interaction and key-exchanges, or some other way?)

Best Regards from Berlin,
Michael

Trminator - I've passed this additional feedback along to the team. Thanks again!

Well, the Browser-Extension could just "tell" the standalone App, where it "thinks" it is located, and the App could then either ASK me, the USER, to verify, that I am running that browser, and want to access my PWs, or check on disk, on that path given? ... either way, it can be verified that the correct browser is talking to the standalone app, without involving huge amounts of development work?!

Hello again Trminator,

I do apologize for any frustration this causes and I can certainly understand how important is to keep 1Password for Windows up to date. I've passed your additional feedback along to the team by way of our tracked issue.

Access to the standalone App's passwords from Google Chrome portable (any version of the browser extension, even current Beta build, which I am currently using) WORKS, as long as the standalone App is Version 8.10.8 or older, but stops working with 8.10.9 or newer...

As previously mentioned, the issue here lies with the app needing to verify where the browser is located on the drive. With your current setup, this is not possible.

The team continues to focus on extending support for trusted web browsers, which we're hoping will help long term for customers using this type of setup or other currently unsupported browsers.

We appreciate your continued patience.

ref: dev/core/core#23060

Hi ag_mike_d,

I don't really get this... the functionality was working fine in 8.10.8, so, I would consider this a regression/bug, rather than a new feature that I'd happily wait for?
Access to the standalone App's passwords from Google Chrome portable (any version of the browser extension, even current Beta build, which I am currently using) WORKS, as long as the standalone App is Version 8.10.8 or older, but stops working with 8.10.9 or newer...
So, yea, the "inconvenience" is that I have not been able to keep up with upgrades to the standalone app since July, 2023, and I'm sure there's some security fixes in that changelog, since then? :((

Hello Trminator,

Please excuse the delayed response.

We have no further news to share about when this extended support for trusted browsers will reach Windows. Please keep an eye on the thread below for new details as they become available:
* Extending support for trusted web browsers — 1Password Community

We're sorry for any inconvenience this has caused.

Hi ag_mike_d , so, what you're saying is, I'm stuck on this by now nearly a year old version of 1Password, until MAYBE a feature currently only available on MAC gets ported to Windows? All because you're unable to fix what ever broke the access from the Portable Chrome? (It was working fine, on 8.10.8, after all ...??) ... Kind of disappointing, not gonna lie...

Hello Trminator,

Thanks for getting back to us.

After looking back to this issue, it was discussed that we verify where the browser is located on the drive. So in this use case it won't work out of the box when running Chrome portable.

It is possible that the upcoming custom browser verification may help with this. Initially this is only available for 1Password for Mac, and hope to see this in the future for other platforms.

You can read more about it in this thread here!

Any news on this?

Hello Trminator - Sorry for the continued issues. I see that the previous support ticket was reopened with your reply. The issue filed with the team continues to be investigated. The team will be in contact with you as soon as possible.

Your patience is appreciated.

ref: dev/core/core#23060