Closed uri closed 6 years ago
I cannot reproduce, my best guess is that an old binary is still alive somewhere on your system at takes over the new binary.
Check the manifest file in either /Library/Google/Chrome/NativeMessagingHosts
or $HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts
, look to which browserpass binary it points. Then try to run that binary with -v
and check the version.
Another test to do is to rename your file from example.com.gpg
to example.gpg
, my guess is that extension will complain on the absence of the url
property in the file, possibly because of the old host app.
I found a file in $HOME/Library/Application Support/Google/Chrome/NativeMessagingHost
com.dannyvankooten.browserpass.json
points to a binary that has the version: Browserpass host app version: 2.0.21
I see what's happening. The login URL I was using was actually redirecting me without me noticing! My bad.
General information
Operating system + version: macOS 10.13.4
Browser + version: Chrome 66.0.3359.181
Information about the host app:
Information about the browser extension:
Exact steps to reproduce the problem
What should happen?
Browser should navigate to https://example.com/login
What happened instead?
Browser navigates to https://example.com