Authentication not persistent

[AuTune]

Signing in works fine for me, it takes about 10 seconds or so for the applet to register I've input the code on the tidal webpage but it does work. However, after a reboot or if I have moved the applet in any way on the panel, it becomes no longer authenticated. Possibly related to #1?

Below is a quick copy of my fastfetch in case anything is obviously incompatible, the browser I am using is Zen Browser.

OS: CachyOS x86_64
Kernel: Linux 6.19.11-1-cachyos
Uptime: 16 hours, 18 mins
Packages: 1316 (pacman), 8 (flatpak)
Shell: fish 4.6.0
Display (LC49G95T): 5120x1440 in 49", 240 Hz [External]
DE: COSMIC 1.0.0
WM: cosmic-comp (Wayland)
Cursor: Adwaita
Terminal: cosmic-term 1.0.8
Terminal Font: Noto Sans Mono (14px)
CPU: AMD Ryzen 7 7800X3D (16) @ 5.05 GHz
GPU: AMD Radeon RX 7900 XTX [Discrete]
Memory: 7.90 GiB / 30.72 GiB (26%)
Swap: 4.04 MiB / 30.72 GiB (0%)
Disk (/): 27.58 GiB / 1.82 TiB (1%) - btrfs
Disk (/storage): 441.63 GiB / 1.82 TiB (24%) - btrfs
Locale: en_US.UTF-8

Let me know any logs I can capture for better testing.

[glima]

Tokens are stored in the system keyring (e.g. GNOME Keyring, KDE Wallet, or the Secret Service backend) via the keyring crate. The entry is under service "cosmic-applet-mare", key "tidal_session". It is a JSON blob containing the full TidalClient session (access token, refresh token, expiry timestamps, user info).

On the shutdown → idle → boot cycle question: yes, it's completely normal for the access token to expire during that cycle — TIDAL access tokens are short-lived (typically ~24 hours). Any other client that does persist more?? I'd love to know.

[AuTune]

Perhaps it operates in a different way on Music Assistant, but when I linked my Tidal account with it, it's stayed connected. Maybe it's refreshing it's own tokens somehow.

[glima]

We do refresh here too, but to refresh we need to be in the validity window of the last given token? No token will live forever.

[AuTune]

You most certainly know more about how token refreshes work, but if mare-player does refresh it's tokens, why do I have to log in every reboot? Like you said, the tokens are valid for 24 hours, I don't ever turn my PC off, I just restart it when I need to. So the window of time where it couldn't refresh itself is minute and unlikely to overlap with the ~24 hour estimate you gave. It persists just fine as long as my PC hasn't been restarted, but always invalidated after every reboot.

[glima]

Again, queued for analysis on next free time. Ty.

[glima]

See if last commit makes it any better. And it's more like 4h, not 24. Anyway, did a couple retries, if network not ready is the issue.