Native messaging application is outdated
See original GitHub issueI just installed pywalfox
on a clean install of Firefox and whenever I start up firefox, I get the following error screen:
However, pywalfox --version
on the command line (which I think is the native messaging application, right?) gives v2.7.1
, the newest version. Do you know what’s going on? This on Ubuntu 18.04, Firefox 83.0
And opening up Pywalfox settings, it is unable to fetch the theme colors (though it can switch between light and dark mode).
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Native Messaging - Chrome Developers
Extensions and apps can exchange messages with native applications using an API that is similar to the other message passing APIs.
Read more >Chrome extensions: is native messaging deprecated?
Chrome browser and the Chrome Web Store will continue to support extensions. Read the announcement and learn more about migrating your app.
Read more >Native messaging - Mozilla - MDN Web Docs
Native messaging enables an extension to exchange messages with a native application, installed on the user's computer. The native messaging ...
Read more >pmacOS+Chrome] Error: Error: Specified native messaging ...
The latest version of Chrome on macOS has resulted in: Error: Error: Specified native messaging host not found. errors with the extension.
Read more >ServiceWorker-backed extensions shut down the Native ...
I would also be interested in the progress of this issue. We have an extension that uses native messaging that syncs our extension...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I suppose we can close it for now. Sorry for not being of more help. I have tried to reproduce the issue on my computer but to no avail, nor do I see anything in the code that would cause this. Most likely it is something with your setup, but the lack of errors makes it really hard to debug. Native messaging has always been a bit tricky to setup because of all the different factors that affect it.
The Mozilla docs are pretty decent and I would suggest to follow the guide there and try to set it up manually.
I hope you can get it resolved!
Ah. Well, thanks for your help. If I figure it out, I’ll come back and update this, but otherwise, I think we can close the issue?