Token issue about abaddon HOT 7 OPEN

if your token doesnt save its probably because you dont have a keyring installed like gnome-keyring or kwallet (or anything supporting the Secret Service API). if you do have one of those installed then that sounds like a bug
so you can either install such a service or alternatively store it in plaintext in abaddon.ini which you can do by adding

[discord]
keychain=false

what issues do you have with voice?

from abaddon.

I'm also on Arch(specifically cachyos) on the latest packages, with kwallet (specifically kde desktop enviroment, with packages kwalletmanager,kwallet-pam,kwallet5,signon-kwallet-extension)
When i attempt to sign in with a qr code i get a error saying the token is invalid, however when i remove the keyring support i'm able to sign in successfully.

from abaddon.

When i attempt to sign in with a qr code i get a error saying the token is invalid, however when i remove the keyring support i'm able to sign in successfully.

that is interesting. so ur saying if you scan the QR code with keychain enabled, it gives you "discord rejected your token" immediately? and if keychain is disabled, it logs in fine? if you manually set a token in the set token dialog and connect, does that work with and without keychain enabled? the code paths for what happens after getting the token should be identical between QR code and manual entry

from abaddon.

that is interesting. so ur saying if you scan the QR code with keychain enabled, it gives you "discord rejected your token" immediately?

Yes

and if keychain is disabled, it logs in fine?

Yes

i've not tried manually inputing the login token, what's the recommended method for obtaining the token and what format does abaddon want the key to be in.

from abaddon.

Yes

strange. ill try and test it myself in a bit

i've not tried manually inputing the login token, what's the recommended method for obtaining the token and what format does abaddon want the key to be in.

log in to discord in a web browser, open the debugging tools (ctrl+shift+i or inspect element), go to the network tab, open a channel, and then select the entry in the network tab that looks like messages?limit=50. under request headers you will see "Authorization." the token is the value of that header

from abaddon.

oh also make sure you are on the latest master. i doubt itll change anything if you are only on the latest release but you never know

from abaddon.