Discord Plugin Re-Authorization after every reboot

[RC-Neko]

I am using cachyOS with KDE Plasma.
My discord is a "normal" package, streamcontroller is installed using flatpak.
Just like described in the other open #49 , I need to make sure to start discord before I start streamcontroller.
Within the plugin settings, it does show "Authenticated successfully"

However, I need to press the validate button and authorize the app within discord before it works properly.

If any more information is needed, please let me know.
Thank you in advance! :)

[Mattdubs9699]

I did some digging into this on my side as well. I think the Discord plugin is initializing twice on StreamController launch and not killing the first RPC connection.

[matt@artix ~]$ flatpak run com.core447.StreamController 2>&1 | grep -i discord
2026-05-15 19:35:11.917 | INFO | src.backend.PluginManager.PluginBase:launch_backend:636 - Launching backend: . /home/matt/.var/app/com.core447.StreamController/data/plugins/com_imdevinc_StreamControllerDiscordPlugin/.venv/bin/activate && python3 /home/matt/.var/app/com.core447.StreamController/data/plugins/com_imdevinc_StreamControllerDiscordPlugin/backend.py --port=35297
2026-05-15 19:35:12.125 | DEBUG | discordrpc.asyncdiscord:connect:44 - Attempting to connect to socket, attempt 1/5
2026-05-15 19:35:12.126 | DEBUG | discordrpc.sockets:connect:40 - Attempting to connect to socket at path: /run/user/1000/discord-ipc-0
2026-05-15 19:35:12.126 | DEBUG | discordrpc.sockets:connect:54 - Connected to socket at path: /run/user/1000/discord-ipc-0
2026-05-15 19:35:14.535 | INFO | src.backend.PluginManager.ActionCore:init:88 - Loaded action Toggle Deafen with id com_imdevinc_StreamControllerDiscordPlugin::Deafen
2026-05-15 19:35:14.535 | INFO | src.backend.PluginManager.ActionCore:init:88 - Loaded action Toggle Mute with id com_imdevinc_StreamControllerDiscordPlugin::Mute
2026-05-15 19:35:16.453 | WARNING | src.backend.PluginManager.EventHolder:add_listener:22 - Callback _update_display is already subscribed to: com_imdevinc_StreamControllerDiscordPlugin::VOICE_SETTINGS_UPDATE
2026-05-15 19:35:16.457 | WARNING | src.backend.PluginManager.EventHolder:add_listener:22 - Callback _update_display is already subscribed to: com_imdevinc_StreamControllerDiscordPlugin::VOICE_SETTINGS_UPDATE

[ImDevinC]

@Mattdubs9699 appreciate the debugging, but it's not attempting to connect twice. It just prints that this is attempt 1 followed by a print statement that says what the path for attempt 1 is

[Mattdubs9699]

Right, sorry! This is an even bigger rabbit hole than I thought. Is this the general flow going on?:

StreamController starts the plugin backend
The Discord RPC socket connects successfully
The plugin immediately tries to proceed with setup/authorization flow
But at that moment, saved access/refresh tokens are not reliably applied yet
So the plugin often falls back to authorize() instead of authenticate()

That causes:

Discord showing an authorization prompt again
StreamController not marking the session as “validated”
No persistent “logged in” state across restarts

[ImDevinC]

The plugin immediately tries to proceed with setup/authorization flow
But at that moment, saved access/refresh tokens are not reliably applied yet

I'll be hoenst, I haven't had time to review the code recently due to other things going on. f you use the debug-extensive-logging branch, it has a large amount of debug logs that are added to the application which may help understand the flow