WebCord 3.8.2 Flatpak broke Wayland screenshare portals

Aknowledgements

• I have checked that there’s no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.

• I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine.

• I have tried running the build from the master branch and it does not have any fixes implemented according to my issue.

• My issue describes one of the unstable and/or not fully implemented features.

• I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

v20.1.3

Application version

3.8.2

Bug description

After updating to v3.8.2 WebCord does not open the usual Wayland screen / app selection window to choose which screen or app to screenshare with others.

Additional context

A temporary solution is to downgrade WebCord by using the command

sudo flatpak update --commit=1d6c868bb18068fac521273dd7afedbd5aeeed5f1d4445fcff5ee191b5a6534e io.github.spacingbat3.webcord

and then masking it to prevent an auto update

flatpak mask io.github.spacingbat3.webcord

[SpacingBat3]

@epetousis This patch doesn’t fix the bug, it behaves the same as reverting MPRIS [commit]. I’ll do a proper fix once I’ll be able to and release patched WebCord version.

[epetousis]

If anyone happens to build from source and is looking for a quick-fix without rolling back, 4e1716c blocks extra CLI feature arguments, and as a result, reverts flags such as --enable-features=UseOzonePlatform and --enable-features=WaylandWindowDecorations, as well as --enable-features=WebRTCPipeWireCapturer, all of which are enabled by default in WebCord. I fixed it with the following patch, but wasn’t sure if this defeated the purpose of the workaround, so haven’t submitted a pull request (but I can if @SpacingBat3 prefers).

diff --git a/sources/code/common/main.ts b/sources/code/common/main.ts
index 0486f07..8082042 100644
--- a/sources/code/common/main.ts
+++ b/sources/code/common/main.ts
@@ -303,7 +303,7 @@ let overwriteMain: (() => unknown) | undefined;
       if(!enabledFeatures.includes(feature)) {
         const disabledFeatures = app.commandLine.getSwitchValue("disable-features");
         if(disabledFeatures === "") {
-          app.commandLine.appendSwitch("disable-features",enabledFeatures);
+          app.commandLine.appendSwitch("disable-features",disabledFeatures);
         } else {
           app.commandLine.appendSwitch("disable-features",disabledFeatures+","+feature);
         }