Snap package working partially and served in the store

[soumyaDghosh]

Hi, I have made a snap package for your app. In my current testing, it works perfectly fine. I have tried with multiple users. It's very easy to maintain, as it's just a wrapper to the deb package.

https://github.com/soumyaDghosh/webcord-snap

Would you like to have this as an official package? Also, you can directly make a snap package from the electron-builder.
https://www.electron.build/configuration/snap.html

EDIT: Also please give me your email id if you want to add you as a collaborator in the snap store.

[soumyaDghosh]

Hii @SpacingBat3 need your help to debug, why screenshare button isn't working and neither giving any error log when pressed. I have found a similar one in your issue list but can't really match

[SpacingBat3]

@soumyaDghosh have you make sure Discord has permission granted for that in WebCord's settings? Also did you check the logs in DevTools console for any clues?

[soumyaDghosh]

The permission for Desktop Capture is given, but, this is what I got in console when pressed screenshare button

9c6ffc3d3bda8510df1a.js:534 [RTCControlSocket] Sending heartbeat
9c6ffc3d3bda8510df1a.js:534 [RTCControlSocket] Heartbeat ACK received
1137398189125812324:1 Uncaught (in promise) DOMException: Could not start video source
Promise.then (async)
T @ b49fb419de93e53ce1c1.js:7902
(anonymous) @ f4cf7a10f9ec65bdf0c4.js:1322
onClick @ f4cf7a10f9ec65bdf0c4.js:1323
Me @ b49fb419de93e53ce1c1.js:1753
je @ b49fb419de93e53ce1c1.js:1753
(anonymous) @ b49fb419de93e53ce1c1.js:1774
Ur @ b49fb419de93e53ce1c1.js:1774
Gr @ b49fb419de93e53ce1c1.js:1774
(anonymous) @ b49fb419de93e53ce1c1.js:1780
cc @ b49fb419de93e53ce1c1.js:1845
Le @ b49fb419de93e53ce1c1.js:1752
Yr @ b49fb419de93e53ce1c1.js:1776
Kt @ b49fb419de93e53ce1c1.js:1759
Zt @ b49fb419de93e53ce1c1.js:1759
r @ 9c6ffc3d3bda8510df1a.js:563
9c6ffc3d3bda8510df1a.js:534 [RTCControlSocket] Sending heartbeat
9c6ffc3d3bda8510df1a.js:534 [RTCControlSocket] Heartbeat ACK received

I tested this by running the snap in devmode, so, networking and other issues aren't there. Cause the sandbox is removed. But, the snap uses the Ubuntu 22.04 as core.

[SpacingBat3]

Is it snap-only issue? Can you test .deb on Ubuntu?

[soumyaDghosh]

It's fine, have fixed it as said before.

[SpacingBat3]

Are you on Wayland? If so, have you installed a package that provides portals for WebRTC PipeWire capturer?

[soumyaDghosh]

In xorg screen sharing is fine. But, in wayland it's making the problems. I was able to find no such package, but I added libwebrtc-audio-processing1. Still it's same. I can confirm, that the package is using portals. Anyway to give you more detailed debugging infos?

[soumyaDghosh]

Hi, I have fixed webcord, just a question. Is there discord-rich presence in webcord?

[Impasse52]

I'm going through the same issue - except I get DOMException: Could not start audio source (rather than video source as in your case). Can I ask you what you did to fix this?

[soumyaDghosh]

I just updated to latest 4.4.0 update, and things fixed 🙃

[Impasse52]

Well, that's discouraging since I'm also on 4.4.0 :/ I suspect this has something to do with the fact that I swapped Pipewire with PulseAudio because of bugs. I'll have to verify this and I'll open an issue if this isn't the case.

update: yep, I confirm that swapping PipeWire and PulseAudio on Fedora 38 makes that error pop out. Don't know how common this can be but I fixed this by running

sudo dnf swap --allowerasing pulseaudio pipewire-pulseaudio
sudo dnf update

and rebooting. Screen sharing now works fine.

[soumyaDghosh]

@SpacingBat3 Can you kindly give me a description for your app, which will somehow mention that this app uses microphone and camera. Also, is it necessary for your app to talk with org.freedesktop.secrets, can you explain a little about why it's needed? Or better if you say it here:
https://forum.snapcraft.io/t/request-to-auto-connect-to-interfaces-for-snap-webcord/36431

[SpacingBat3]

Given users don't need (additional) sandboxing to manage microphone/camera access, I guess the accurate and future-proof description would be microphone/camera access management for Discord as of the usage reason. WebCord should always firewall this access internally anyway and forbid access as sane defaults, eventually asking the users for the permission for the first time once Discord wants to access it. Also org.freedesktop.secrets are used for the encryption (e.g. configs, CSS themes, maybe cookies as well with modified Electron binaries via fuses) and given Electron doesn't really expose an API (see safeStorage API in Electron docs for more info) that allows me to read any kind of passwords (at least for now), I can't really use that for evil purposes even if I wanted to, at least without any additional libraries. Discord should not have access to FreeDesktop secret service directly, it's the Chromium that does that.

[soumyaDghosh]

So, what should I add in the description?

A discord and spacebar client for voice & video calls and text messages. Made with Electron in Poland.

[SpacingBat3]

EDIT: Also please give me your email id if you want to add you as a collaborator in the snap store.

As of my email, you can use the same as in commits or my GitHub account. But I'm not sure exactly what you mean by email id… Could you explain it a bit more?

[soumyaDghosh]

I want to add you as a collaborator in the snap store for the snap package, meaning giving you full access to the snap package. And eventually transferring the ownership to you if you want now/in future.
So, email id means the email address where I/anyone can send you mail messages.

[soumyaDghosh]

Sent you a collaboration request in your mail address that I got in github:
git@spacingbat3.anonaddy.com

[SpacingBat3]

As I'm neither snap guy nor flatpaks, don't expect me to contribute here a lot. I'll possibly still find it more as a community package, even if I'm involved into it (mostly due sandboxing that might break a lot of stuff – in the past it did with the Flatpaks, now they're a little more mature AFAIK).

[soumyaDghosh]

Ohh sure! no problem! But kindly finalize the description.

[soumyaDghosh]

@SpacingBat3 kindly finalize the description