Currently used account gets removed when computer goes to sleep

[MysticAx0lotl]

Describe the bug
Whenever I put my computer into sleep or hibernate mode without closing Armcord from the tray, when I turn the computer back on it will show a login prompt stuck on an infinite loading screen. When fully restarting ArmCord, whatever account was logged in is completely gone. I initially thought that this was a KDE issue, but it exhibits the same behavior under Windows. I've tested on a desktop and two laptops.

To Reproduce
Steps to reproduce the behavior:

1. Launch ArmCord
2. Put the device to sleep (e.g. if you're on a laptop, close it)
3. Turn the machine back on
4. Restart ArmCord from the tray

Desktop

• OS: EndeavourOS Galileo + KDE | Windows 10 LTSC
• Method of installation: AUR | Latest Github release
• Version: 3.2.5
• Note: The desktop and one laptop have NVIDIA GPUs (the laptop has a Quadro m520, the desktop hasa GTX 1050i). However, the other laptop with no GPU still shows the same behavior

[nyxiereal]

I'm having the same issue on EndeavourOS on my laptop. It works perfectly when I'm on my PC tho.

[gusio]

Se issue here - windows 10. It doesn't seem to have to do with sleep mode in my case - just randomly launches with empty server lists / friends and chat lists (it does maintain my personalized theme though)

I do have an official discord client installed so maybe it gets confused with some config files... not sure

The solution is just restarting armcord - the second time in a row it usually loads my account correctly

[MysticAx0lotl]

The solution is just restarting armcord - the second time in a row it usually loads my account correctly

For me, it logs me out of the account completely, and I have no other client installed.

An interesting thing I found is when I went into "Devices" under my account setting, I found that every time I had to re-login to ArmCord with my computer, it counted as a new device. My computer also turns off its wifi when it goes to sleep, maybe it's an IP address thing?

Edit: by "IP address thing", is it possible that the (possible) change in IP address messes with the login token?

[nyxiereal]

Now on my windows desktop I have to close and reopen it for it to work. On my Linux laptop it sometimes starts logged it, sometimes not.

[MysticAx0lotl]

Currently I've done some testing and found this also occurs with Vesktop, which leads me to believe it's either an issue with KDE or Electron. I will be submitting issues to both Github repositories when I can

[MysticAx0lotl]

Update: I've ruled out KDE as an issue. I observed this same behavior on an unmodified Arch install running LXQt, which means this is looking more and more like an Electron issue. However, there is one more shared element between KDE, LXQt, and the custom clients I've tried: gnome-keyring, which I had to install for compatibility with things like Github Desktop. Could that be causing this issue?