CoApp not recognized

[BoilerinTX]

Your question

Can someone smarter than me give me a hand? Here are my particulars.

CoApp Not Recognized.pdf

Addon & CoApp version and details

version: 9.5.0.1
target: google
channel: stable
lang: en-US

CoApp - It says it isn't installed, but it is! The latest download has been installed

[jcfrog]

Hi,
If the coapp is properly installed but the extension can't see it it might be an issue with antivirus or firewall, something is blocking downloadhelper process.

[innovate2000]

I am on OpenSuse Leap 15.6 and have turned off apparmor and the firewalld to see if the CoApp would be recognized - no luck (I've since turned them back on). I have been having this problem for WELL over a year now (perhaps 2 or 3 years - perhaps more) - HOPING that it would eventually get resolved - but it hasn't. The extension USED to work flawlessly (in Waterfox - I've been using Waterfox since it's inception) - until more than a year ago it just stopped working and I've not used it since. I've reinstalled more than 20 times by now. I used to LOVE the extension, so I'd like to resolve the issue if possible.

The browser: Waterfox 6.5.9 (64bit)
OS Linux: OpenSuSE 15.6 (64bit) - up to date
Link to the coapp you installed?: ~/.local/share/vdhcoapp/vdhcoapp
Linux: flatpak & snap are BOTH installed - BUT I PRIMARILY use snap (as stated previously, system completely up to date)
On Linux, the output of /opt/vdhcoapp/vdhcoapp --info:
{
"id": "net.downloadhelper.coapp",
"name": "VdhCoApp",
"version": "2.0.19",
"binary": "/home/MYUSERNAME/.local/share/vdhcoapp/vdhcoapp",
"displayName": "VdhCoApp",
"description": "Video DownloadHelper companion app",
"target": {
"os": "linux",
"arch": "x86_64",
"node": "18"
},
"home": "/home/MYUSERNAME",
"converterBinary": "/home/MYUSERNAME/.local/share/vdhcoapp/ffmpeg",
"converterBase": "ffmpeg",
"converterBaseVersion": "c30f360"
}

I ALSO added "/opt/vdhcoapp/vdhcoapp ux" (without the quotes) to TWO NEW FILES: /etc/apparmor.d/local/usr.bin.firefox and /etc/apparmor.d/local/usr.bin.waterfox (I HOPE that's what the instructions on "https://www.downloadhelper.net/w/CoApp-not-recognized" were prompting me to do).

[Mattmjs]

The first thing to consider is that forks of Firefox don't automatically have the native messaging hosts. You have to copy that from
Firefox to the directory for Waterfox. Even if this step has been done, snaps and flatpacks run in a sandbox.
The snap firefox has a permission that pops up that you have to allow to make it work, maybe that's what waterfox needs.
I've seen someone mention flatseal is needed if it's a flatpack to allow some permission. Search the forum on that.

[innovate2000]

Thanks for responding. An interesting thing I stumbled upon is that Chrome recognizes the CoApp as is - no adjustments necessary - which lends itself to @Mattmjs' answer that the issue resides with Waterfox and its internals. I'll do more research on this and post my findings, if any.