Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebCord blocks StreamKit overlay

See original GitHub issue

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

20.0.0

Application version

v3.7.1

Bug description

While WebCord is running the StreamKit Overlay fails to connect. If both WebCord and the native Discord client are launched at the same time then the overlay fails to connect to the native client until WebCord has been closed.

Additional context

I personally have 2 Discord accounts, my main running in WebCord and my second account in the native Discord client and my secondary account I use for streaming and use the overlay kit with it but because of this bug I have to close WebCord while I’m streaming.

https://user-images.githubusercontent.com/39580303/184503138-f085fb0f-8130-4c2c-91ac-417a9f14d202.mp4

Issue Analytics

State:
Created a year ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

SpacingBat3commented, Aug 21, 2022

@3e849f2e5c I’ve reported the bug to Discord, hopefully they will improve their implementation of WebSocket client on StreamKit to solve this so it will ask Discord client once WebCord closes the connection.

1reaction

SpacingBat3commented, Aug 14, 2022

I’ll close this as wontfix, WebCord does not support requests that requires API to be resolved (SteamKit wants from WebCord to respond to AUTHORIZE request) and it is in general a bug on the Discord’s side (I’ve described why I think that way in previous comment). As a side note, I believe setting up any WebSocket Server (without caring about the communication at all) has potential to be a denial-of-service for Discord client, blocking entire communication for stuff like RPC (based on WebSocket; Discord also uses IPC for RPC), invite links etc.