JabRef version
5.8 (latest release)
Operating system
macOS
Details on version and operating system
OSX 12.6
Checked with the latest development build
Steps to reproduce the behaviour
Importing references through the browser extension fails when JabRef is installed to ~/Applications on MacOS. This initally seems like it occurs because org.jabref.jabref.json points to the wrong path but the issue continues after this is fixed because the hardcoded path in jabrefHost.py points to the system Applications directory.
Steps to reproduce:
- Install JabRef to ~/Applications
- Install browser extension (tested on firefox)
- Try to import a reference
I manually fix this each install by hardcoding the application path in jabrefHost.py to point to ~/Applications/JabRef.app/Contents/MacOS/JabRef. Similarly the correct path must be set in the JSON when installing the browser extension itself.
I noticed the comment above the path in jabrefHost.py (which doesn't work correctly on Mac) so possibly it's hard to automatically detect the location. Similarly, the JSON is necessarily hardcoded I imagine. If so, it would at least be useful to say for how to correct the problem in the browser extension install instructions.
Appendix
...
Details
Only a generic error is produced:

JabRef version
5.8 (latest release)
Operating system
macOS
Details on version and operating system
OSX 12.6
Checked with the latest development build
Steps to reproduce the behaviour
Importing references through the browser extension fails when JabRef is installed to ~/Applications on MacOS. This initally seems like it occurs because org.jabref.jabref.json points to the wrong path but the issue continues after this is fixed because the hardcoded path in jabrefHost.py points to the system Applications directory.
Steps to reproduce:
I manually fix this each install by hardcoding the application path in jabrefHost.py to point to ~/Applications/JabRef.app/Contents/MacOS/JabRef. Similarly the correct path must be set in the JSON when installing the browser extension itself.
I noticed the comment above the path in jabrefHost.py (which doesn't work correctly on Mac) so possibly it's hard to automatically detect the location. Similarly, the JSON is necessarily hardcoded I imagine. If so, it would at least be useful to say for how to correct the problem in the browser extension install instructions.
Appendix
...
Details
Only a generic error is produced: