Failing to load after update

[FIRECATinBLACK]

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

armv7l (32-bit ARM)

Electron version

v20.1.0

Application version

v3.8.1

Bug description

downloaded webcord a few months ago through piapps (if I read the logs right it clones straight from github) and it worked perfectly right away. Just tried to try a different discord version, freecord in the settings and whenever it was selected webcord would tell me that my raspi isnt connected to the internet (my connection was completely fine and it immediately worked again upon switching back to stable discord. I switched back to freecord but after it still didnt load I remembered that there was a update due so I updated it through piapps. Upon starting webcord back up I am now stuck on the "cannot connect to discord service, please make sure you're connected to the internet" error with no way to see if its because I updated (wich fully reinstalled webcord according to logs again) while on a seemingly broken discord version or just the update being broken in general because the option to switch between those discord versions is gone for me

Additional context

if this is in any way relevant I am running webcord on a raspberrypi 4, raspberry os with desktop (linux debian), armv7 structure

[SpacingBat3]

This bug you're occuring is traight consequence of multiple breakages done in WebCord's code (maybe this feature was put in advanced for a reason) according to Fosscord instances. To summarize this:

• Freecord instance is broken and disabled from being accessed via GUI.
• Instances are missing from the configuration menu due to the bug (see Fosscord Docs #239). You can downgrade to the older WebCord or just remove the ~/.config/WebCord to remove the application's data.

It's kinda not a bug with the application, but a result of a few actions done to it and causing a breakage. I don't think I will work on it in other way than just releasing a new version of WebCord with the fixes mentioned in #239.