Forum Discussion

Trminator's avatar
Trminator
Occasional Contributor
3 years ago

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

Hi, since the most recent release of 1Password's Chrome Extension (2.12.0 and newer) my Extension is unable to connect to the desktop App, ONLY from the Chrome Portable I use. My "normal" Chrome in...
windows
Trminator's avatar
Trminator
Occasional Contributor
3 days ago

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

1P_Dave's avatar
1P_Dave
Icon for Moderator rankModerator
3 days ago

Trminator​ 

Thanks for following up. 1Password verifies where the browser is located on the drive for security reasons before connecting to it. This isn't something that the team is planning to change at the moment. Chrome Portable also appears to be an unofficial and modified version of Chrome, only the official release from Google is supported. 

It's possible that the additional browser feature that we're building for Windows, which allows you to add unsupported browsers to the 1Password for Windows desktop app, might help here but the feature is still being built and this would need to be tested once the feature is built and released.

-Dave

Issue=GA-92075