Specified native messaging host not found

[moseify]

I executed all the steps in the instructions manual but no use and still getting this nuisance error

[mczakk]

I have exactly the same error using chrome on windows, i have followed the instructions to the letter. The extension also fails to work on firefox on the same machine

[dcecchini]

I have the same error using Edge Version 103.0.1264.62 (Official build) (64-bit). When I open the browser console, there is only a warning message, no error:

But in the previous tab, there is a message saying that the documents to be parsed are zero:

So I think it may be the case that it could not find the information of the paper in the page (both Google scholar page and SSRN page).

[tobiasdiez]

I'm sorry for the inconvenience caused. This error points to an issue with the config, but sadly the browsers don't give much detail about the particular problem. https://developer.chrome.com/docs/apps/nativeMessaging/#native-messaging-debugging suggests to check the following:

• Is the name spelled correctly in the extension and in the manifest file?
• Is the manifest put in the right directory and with the correct name? See native messaging host location for the expected formats.
• Is the manifest file in the correct format? In particular, is the JSON syntax correct and do the values match the definition of a native messaging host manifest?
• Does the file specified in path exist? On Windows, paths may be relative, but on OS X and Linux, the paths must be absolute.

So I guess the manifest file is not in the correct path.

[physicsbeany]

Was this ever resolved? It only just happened to me yesterday, after several months of issue-free use of JabRef on my MacOS machine (with Chrome). Could Chrome browser updates have messed up the JabRef configuration?