Native messaging between Brave extension and the host app is not working

dero
dero
Community Member
edited November 4 in 1Password in the Browser

I've tried to figure out why the 1Password extension in Brave is unable to communicate with the 1Password host app for a long time today. Now I give up and kindly ask for help.

When I add the extension to my Brave browser, I'm seeing the "Connecting to Desktop App" message and a spinner. The connection never successfully finishes.

I'm a software engineer myself, so here are the things I tried unsuccessfully:

Checked the extension console for errors:

💫 Looking for desktop app com.1password.1password
📤 Sending <NmRequestAccounts> message to native core <509228836>
Unchecked runtime.lastError: The message port closed before a response was received.
⏳ Timeout waiting for response to <NmRequestAccounts> from native core <509228836>

Checked the browser support logs in /logs/BrowserSupport:

Sometimes I'm getting:

INFO  2024-10-23T12:52:16.486+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src/main.rs:254] Starting 1Password-BrowserSupport 8.10.50-8.BETA production build no. 81050008.
INFO  2024-10-23T12:52:16.516+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:62] Verifying browser "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe"
INFO  2024-10-23T12:52:16.531+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:81] name: brave, publisher: Brave Software, Inc., pid: 13296, version: 130.1.71.114
INFO  2024-10-23T12:52:16.597+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:153] Starting SLS communication (attempting connection to desktop app)
ERROR 2024-10-23T12:52:16.597+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:201] Failed to connect to the main app: Io(Os { code: 231, kind: Uncategorized, message: "All pipe instances are busy." })
INFO  2024-10-23T12:52:16.598+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:222] Desktop app not running, no connection established
INFO  2024-10-23T12:52:16.598+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:559] Attempting to re-establish a connection to the 1Password app
WARN  2024-10-23T12:52:16.598+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:484] Tried to re-establish connection with the 1Password app (but it might not have been running): Io(Os { code: 231, kind: Uncategorized, message: "All pipe instances are busy." })
INFO  2024-10-23T12:52:16.599+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:245] Reached end-of-stream for receiving messages from b5x. Ending SLS communication.
INFO  2024-10-23T12:52:16.599+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src/main.rs:272] Shutting down 1Password-BrowserSupport 8.10.50-8.BETA production build no. 81050008.

Other times just:

INFO  2024-10-23T13:10:30.196+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src/main.rs:254] Starting 1Password-BrowserSupport 8.10.50-8.BETA production build no. 81050008.
INFO  2024-10-23T13:10:30.227+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:62] Verifying browser "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe"
INFO  2024-10-23T13:10:30.239+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:81] name: brave, publisher: Brave Software, Inc., pid: 13296, version: 130.1.71.114
INFO  2024-10-23T13:10:30.296+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support-lib\src\communication_logic.rs:153] Starting SLS communication (attempting connection to desktop app)

The "All pipe instances are busy" error is interesting, but even closing the pipes manually via Powershell, then fully restarting all 1Password and Brave processes didn't lead to any improvement.

I also used ProcMon to check the communication between the browser and the 1Password-BrowserSupport.exe process and everything seemed relatively OK, but I wasn't able to observe any "CreatePipe` events, which I found odd.

I also made sure all values within browser_support_manifest_chrome.json are correct. I even created browser_support_manifest_brave.json with a trimmed down and confirmed correct values, even with full paths as opposed to relative paths, then changed the path in Windows registry to make 1Password use that manifest instead. To no avail.

This all started out of a sudden.

I find it interesting that the extension worked in Chrome, but when I uninstalled it and reinstalled it to test if it would still work, it stopped working (!) as well with the same symptoms.

I tested this with both 1Password stable and 1Password beta.

Any assistance will be greatly appreciated. I rely on the browser integration heavily for my work.

1Password Version: 8.10.50
Extension Version: 8.10.48.25
OS Version: Windows 10
Browser: Brave Version 1.71.114 Chromium: 130.0.6723.58

Comments

  • Dunecat
    Dunecat
    Community Member

    It's been almost 2 weeks since you reported this and I haven't seen any updates. Is it still broken?

  • EvonG1P
    EvonG1P

    Hello, @dero. Thank you for reaching out. I'm sorry about the app integration problem you are encountering with 1Password.

    So that I can take a closer look at the issue you are experiencing with the 1Password desktop app communicating with 1Password in the browser, I would like to request that you send us some information to support+forum@1Password.com. With your email, please include the following:

    1. First, please recreate the issue you are experiencing.
    2. Generate a diagnostic report from the 1Password app and the 1Password extension using the steps here -> How to send a 1Password diagnostics report
    3. Attach both files to your email.

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here, and I will be able to locate your message and ensure it has reached the right place. Thank you!

    @Dunecat,

    If you're encountering the same problem as @dero, I encourage you to send us an email and follow the steps I've outlined above. The team and I are happy to investigate the issue you're experiencing.

    -Evon