Keeping showing "Verifying Companion App..." on Linux about vdhcoapp HOT 6 CLOSED

The companion app on the github repository is the one we compile and distribute, so i am reasonably confident that the overall system is working.
You may want to recheck all possible manifest locations so that you don't have left a corrupted manifest somewhere, try on Chrome as you may have a more explicit error/warning message in the browser console, ...

from vdhcoapp.

I just tested on Chrome & Chromium:

1. They also keep hanging at Verifying Companion App..., but after clicking Recheck many times, it said `

Companion App not installed
Checking companion app returned: Native host has exited.

2. Console of the browsers shows nothing.
3. ~/.config/google-chrome/NativeMessagingHosts looks like this:

You may want to recheck all possible manifest locations so that you don't have left a corrupted manifest somewhere

BTW, what is the expected output after executing net.downloadhelper.coapp-linux-64 ? I run it without ARGV, it hangs without any output. (Surely I can see VdhCoApp: VdhCoApp is ready to be used if with install argument)

from vdhcoapp.

The problem has not been reported for 2 years. Closing the issue.

from vdhcoapp.

I'm having this issue today.

from vdhcoapp.

Provide some hints to debug such issue under Linux + Firefox. Though this time the error message I've encountered is An unexpected error occurred instead of Verifying Companion App.., but may be still helpful for somebody.

According to MDN https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests

Steps:

1. check if the following files exist:

/usr/lib/mozilla/native-messaging-hosts/<name>.json
~/.mozilla/native-messaging-hosts/<name>.json   # ATTENTION: This one has higher priority.

2. Check the content of these json files.

// $ cat /usr/lib/mozilla/native-messaging-hosts/net.downloadhelper.coapp.json 
{
    "name": "net.downloadhelper.coapp",
    "description": "Video DownloadHelper companion app",
    "path": "/usr/bin/vdhcoapp",
    "type": "stdio",
    "allowed_extensions": [
        "[email protected]",
        "{b9db16a4-6edc-47ec-a1f4-b86292ed211d}"
    ]
}

And try to run the executable in path to test if it's no problem.

@mi-g Sorry for trouble you, just curious that when running /usr/bin/vdhcoapp, is it on purpose that no any error message, log, diagnostic info or help message on stdout? If so, wondering that some log may be easier for those who needs troubleshooting, at least can confirm that vdhcoapp itself is everything ok. Thanks.

from vdhcoapp.

when running /usr/bin/vdhcoapp, is it on purpose that no any error message, log, diagnostic info or help message on stdout?

Yes, it is on purpose. The reason is that the coapp is "passive" and controlled by your browser. They communicate via stdin/stdout, so the coapp can't just print anything, as its stdout is used as a communication socket.

Now thinking about it … we could show some info via stderr. I filed an issue: #170.

from vdhcoapp.