WebCord: Error while decrypting the chipertext provided to safeStorage.decryptString
Aknowledgements
-
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.
-
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
masterwhich 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
🪟️ Windows
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
Can’t run it, so whatever’s packaged with v4.2.0
Application version
v4.2.0
Bug description
I’m getting the following error when installing:
This is a fresh Windows 11 installation, so I might be missing some dependencies, even low-level ones. I remember everything was working fine before re-installing Windows, which is basically the only reason why I think I might be missing something.
Additional context
No response
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 19 (3 by maintainers)
A temporary fix that I found is to delete the windowState file, located at %AppData%/WebCord/ in Windows.
Same issue on Arch Linux, both in the
webcordandwebcord-binpackages (config files not purged in-between testing both packages, which may explain why the issue persisted on an otherwise fresh install of webcord). DeletingwindowStatein~/.config/WebCordseems to have resolved the problem for now.Worth noting that I was not having this issue prior to updating today.
I should be saying, Flatpak builds are not supported by me at all ocommunity maintains them, so don’t expect from me fixing any bugs specific to them) and spamming that this issue still happens, especially in case of the Flatpaks, is not helpful at all.