Gnome-shell-extension-gsconnect: Chromium in Snap packet reports "Service Unavailable"

[nalsubaie74]

Describe the bug
Service unavailable on chromium extension. Chromium version 74.0.3729.131 installed via snap
To Reproduce
Steps to reproduce the behaviour:

1. Go to the web browser
2. See error: stop sign on extension icon, message "service unavailable" on clicking on the icon
   Please note that the DE version is working with no problems

Debug output

Context
background.html
Stack Trace
js/background.js:62 (postMessage)
js/background.js:79 (onPopupMessage)
js/browser-polyfill.min.js:1 (anonymous function)

Snipped by @andyholmes

System Details (please complete the following information):

• GSConnect version: 7
  
  
  
  • Installed from: chromium extensions
  
  
• GNOME/Shell version: 3.32
• Distro/Release: Ubuntu 19.04

GSConnect environment (if applicable):

• Paired Device(s): Samsung S9
  -KDE connect: 1.12.7

[andyholmes]

Thanks for reporting. I'm not sure what you mean by "DE version is working properly". Do you mean that the browser extension works in a regular .deb version of Chromium, but not a snap version?

[nalsubaie74]

Apologies for the lack of clarity. GSconnect is working beautifully on my computer. My issue is with the chromium extension

[nalsubaie74]

Interestingly, the extension on firefox (deb installation) works. I wonder whether it is something to do with snap privileges on my device

[andyholmes]

It's possible. The WebExtension need to execute the nativeMessaginHost.js program, which is usually located at:

~/.local/share/gnome-shell/extensions/[email protected]/service/nativeMessagingHost.js

It gets this from the manifest file at:

~/.config/chromium/NativeMessagingHosts/org.gnome.shell.extensions.gsconnect.json

I'm not familiar with snaps, but I know there are some difficulties with flatpaks in some situations. You might want to close Chromium, open GNOME Logs, then re-open Chromium and see if any errors are logged about this (assuming snaps log in the same place).

[nalsubaie74]

the extension works with no issues on a non snap chromium nstallation. It must be something to do with snap permissions.
The issue is closed for me but someone may wish to advise on changing snap permissions to allow for GSConnect extension to work.
Many thanks Andy for a great application and the prompt response to the query.

[andyholmes]

Okay, I'l retitle this and leave it open in case anyone else knows more about this issue.

[andyholmes]

Going to close this one since there's been no sign of someone knowing the answer, and strictly speaking it's not our bug :)