From 8df8cf846fa7fe16349b389330beba9845d3e6bb Mon Sep 17 00:00:00 2001 From: Siedlerchr Date: Tue, 11 Aug 2026 22:14:22 +0200 Subject: [PATCH 1/2] docs: add native messaging troubleshooting --- en/collect/jabref-browser-extension.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/en/collect/jabref-browser-extension.md b/en/collect/jabref-browser-extension.md index e4c153b2f..ff99fa61d 100644 --- a/en/collect/jabref-browser-extension.md +++ b/en/collect/jabref-browser-extension.md @@ -172,6 +172,17 @@ With Firefox installed as a flatpak: 3. Check that the Python script works. In Terminal run `/Applications/JabRef.app/Contents/Resources/jabrefHost.py`. If there are no errors the script is working properly. Stop the script by pressing `Ctrl + D`. +#### Native messaging host not found in Chrome + +If Chrome reports `Specified native messaging host not found.`, its registered JabRef host manifest may refer to an old location for `jabrefHost.py`. Reinstall the manifest bundled with the currently installed JabRef application: + +```sh +sudo cp "/Applications/JabRef.app/Contents/Resources/native-messaging-host/chromium/org.jabref.jabref.json" \ + "/Library/Google/Chrome/NativeMessagingHosts/org.jabref.jabref.json" +``` + +Quit Chrome completely and reopen it afterwards. This assumes JabRef is installed in `/Applications`; adjust the first path if it is installed elsewhere. + #### Local JabRef installs org.jabref.jabref.json directs the browser extension to a python script in the JabRef app, which is set to the most common install path by default (`/Applications/JabRef.app/Contents/Resources/jabrefHost.py`). If you have installed JabRef somewhere else, most likely to your local applications folder (`~/Applications/JabRef`), then you will need to update this path to the correct location. For example, in local installs this would be `/Users/USER/Applications/JabRef.app/Contents/Resources/jabrefHost.py`, where `USER` is your username. From 0acb70031774d3837c6fe3bbe903c738a09ccc72 Mon Sep 17 00:00:00 2001 From: Siedlerchr Date: Wed, 12 Aug 2026 22:21:58 +0200 Subject: [PATCH 2/2] add user install path as well --- en/collect/jabref-browser-extension.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/en/collect/jabref-browser-extension.md b/en/collect/jabref-browser-extension.md index ff99fa61d..7cc50e187 100644 --- a/en/collect/jabref-browser-extension.md +++ b/en/collect/jabref-browser-extension.md @@ -174,13 +174,24 @@ With Firefox installed as a flatpak: #### Native messaging host not found in Chrome -If Chrome reports `Specified native messaging host not found.`, its registered JabRef host manifest may refer to an old location for `jabrefHost.py`. Reinstall the manifest bundled with the currently installed JabRef application: +If Chrome reports `Specified native messaging host not found.`, its registered JabRef host manifest may refer to an old location for `jabrefHost.py`. Reinstall the manifest bundled with the currently installed JabRef application in the Chrome manifest location you use: + +* For a system-wide Chrome installation (all users), run: ```sh +sudo mkdir -p "/Library/Google/Chrome/NativeMessagingHosts" sudo cp "/Applications/JabRef.app/Contents/Resources/native-messaging-host/chromium/org.jabref.jabref.json" \ "/Library/Google/Chrome/NativeMessagingHosts/org.jabref.jabref.json" ``` +* For a per-user Chrome installation (current user only), run: + +```sh +mkdir -p "$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts" +cp "/Applications/JabRef.app/Contents/Resources/native-messaging-host/chromium/org.jabref.jabref.json" \ + "$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts/org.jabref.jabref.json" +``` + Quit Chrome completely and reopen it afterwards. This assumes JabRef is installed in `/Applications`; adjust the first path if it is installed elsewhere. #### Local JabRef installs