Closed 4164696f73 closed 1 year ago
Possibly a duplicate of #371 (what's your CSP settings?).
You mean this?
Would be cool to add a small note, because this is actually what was causing the issue... Google Storage API is required for that.
You mean this?
Would be cool to add a small note, because this is actually what was causing the issue... Google Storage API is required for that.
That's the reason why these are in Advanced section – whatever you disable in CSP, it is expected you will end up with breakages. If disabled everything (like in your case), you might notice GIF picker not working, a lot of embeds not loading (YouTube videos, Spotify player etc.), even uploads are not functioning as new Discord implementation uses Google Storage API (in the past Discord uploaded images directly and did not depend on Google stuff).
Aknowledgements
[X] I have checked that there is no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
[ ] This bug affects Discord website.
[X] This issue is confirmed to be reproduceable when WebCord is packaged on at least all three latest supported Electron major releases.
[ ] This issue is reproduceable in Chrome, Chromium or any Chromium-based browser, e.g Brave or Edge (please write in Additional Context which browser you have used if it is neither Chrome nor unmodified Chromium).
[ ] There are no fixes done to
master
which resolves this 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
25.2.0
Application version
4.3.0
Bug description
Can't publish any screenshots via Webcord, going to Discord website works flawlessly. All I get is long loading, and then "an error occurred".
Not sure if this is tied to Flatpak or not, though. Couldn't fix it with permissions etc.
Additional context
No response