unable to establish connection (Latest Beta)
This was working ....
Mac 10.14.5
1Password 7
Version 7.3.2.BETA-0 (70302000)
1Password Beta
1Password X
1Password X Beta – Password Manager
1.16.6
My 1Password X log ...
Initializing Desktop App Integration. Attempting to connect to native app.
Connecting to native app 2bua8c4s2c.com.agilebits.1password
Preparing hello payload for device xxxxxxxxx:
(accountUUID, userUUID, server) => (xxxxxxxx, xxxxxxxxx, 1password.com)
Native app port disconnected. Error: Specified native messaging host not found.
Signing payload for account xxxxxxxxx with kid xxxxxxxxx
Sending message to native app
Failed to send because our port was disconnected. Browser code signature became invalid?
I restarted both Mac 1Password (including mini) and browser .. same issues
Thanks
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
Hi @rr0ss0rr – sorry to hear about the trouble! Could you let me know what browser you're using as well as the version number? I know Chrome had an update recently, which causes the code signature to become invalid in 1Password's eyes, but a restart of the browser should have fixed that.
0 -
oops ... Vivaldi 2.6.1566.44 (Stable channel) (64-bit)
0 -
Hey @rr0ss0rr ,
I'm not entirely sure if this is indeed a NativeMessagingHost problem or a browser verification problem. Make sure that your Vivaldi is up to date and try the following: https://support.1password.com/kb/201707/#what-you-should-do
Let us know if that did the trick.
0 -
Yaron .. Thanks .. it was indeed ~/Library/Application Support/Google/Chrome ... I removed the Chrome browser and removed the Google directory in Application Support. Is it possible for 1Password X to validate and display an appropriate error in the log or even in Preferences when you enable Mac Integration?
Richard
0 -
Awesome! Glad Yaron was able to help. :+1:
It's a good idea, but it isn't possible for 1Password to know why it isn't connected -- in this case because Native Messaging wasn't available in the browser at all -- as there are a wide range of causes. But we're always here if you need us. :)
0
