Forum Discussion

moiraine_sedai's avatar
moiraine_sedai
Occasional Contributor
4 years ago

can’t verify the identity of your browser since latest few chrome beta releases

IIRC, the beta version of google chrome recently changed the app name to "Google Chrome Beta.app", and its identifier has changed from "Identifier=com.google.Chrome" to "Identifier=com.google.Chrome....
browser extension
moiraine_sedai's avatar
moiraine_sedai
Occasional Contributor
4 years ago

Hi @"jack.platten"

Thanks for getting back; In my system I only have the beta of chrome; 1 password is

  • not working when the beta app is named "Google Chrome Beta.app"
  • since the trouble shooting app is unable to find chrome when it's named "Google Chrome Beta.app", I also tried changing the beta app bundle to "Google Chrome.app" (hence the ps output above), then troubleshooting app finds the correct chrome version, but still report it's not running, and 1pw is still reporting unable to verify browser.

After some digging around, what worked is to make a folder in ~/Library/Application Support/Google/Chrome/NativeMessagingHosts and copying over the json file, like this. Looks like there's some changed since the last couple beta of chrome that causes this issue, possibly due to the data folder for chrome beta is moved from ~/Library/Application Support/Google/Chrome to ~/Library/Application Support/Google/Chrome Beta

In this case, 1pw to throw the "can’t verify the identity of your browser" message (instead of the could not connect for Canary version in the linked documentation)