mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #815] App shows correct startpage but does not seem connected otherwise #1422
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1422
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sorodon on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/815
Describe the bug
Arch (EndeavourOS) with kitty terminal
When opening the App it shows my start page with my playlists but selecting anything sends be to an eternal loading screen.
No playback is shown and the device selection is empty.
However other devices (like my phone) show the app in spotify-connect and it is selectable. When it is selected, the music is paused instantly when hitting play though.
Even more weird:
Uninstalling and installing (via pacman) again did not help at all. I deleted (as in moved and renamed) all config files but for some reason the app seems to remember my account and is able to show my startpage.
Log shows errors about token being invalid, but I don't understand it fully
To Reproduce
For me: Simply opening the app, but I doubt this works for other PCs
Expected behaviour
I'd like to play music again
Log and backtrace
Log
(The Client and Device IDs were redacted by me)Screenshots
Environment
pacman -S spotify-player@feakuru commented on GitHub (Aug 27, 2025):
same here on Arch. might this be connected to the latest
librespotbump?@megakitsu commented on GitHub (Aug 27, 2025):
Same on fedora, agreed think it's librespot
@arc-d3v commented on GitHub (Aug 27, 2025):
Edit : Seems related to https://github.com/hrkfdn/ncspot/issues/1681
@TimVosch commented on GitHub (Aug 27, 2025):
I fixed it by changing the librespot-playback in
spotify_player/cargo.tomltoFor completion sake:
@aome510 commented on GitHub (Aug 27, 2025):
hi folks, please refer to my comment in https://github.com/aome510/spotify-player/issues/802#issuecomment-3218342832.
0.7.0is broken so please use the latestmasterif possible.Not sure why this is needed. What is the error if you just run latest
masteras-is?@TimVosch commented on GitHub (Aug 27, 2025):
There was no playback device and these errors popped up in the log. I am using master as-is here.
By changing the librespot-playback dependency it is solved and playback device is available again, and the errors are gone.
I don't know why, but this is taken from the previously mentioned ncspot commit (https://github.com/hrkfdn/ncspot/issues/1681) as mentioned by @arc-d3v .
https://github.com/aome510/spotify-player/issues/802#issuecomment-3218342832 unfortunately does not solve this issue. It appears to be separate.
@aome510 commented on GitHub (Aug 27, 2025):
Good to know, thanks. I will keep that in mind before releasing a new version
@TimVosch commented on GitHub (Aug 27, 2025):
If it would help you I can send you DEBUG logs, but privately due to all the tokens and sensitive information in there. Let me know how to get those to you.
@aome510 commented on GitHub (Aug 27, 2025):
No it's fine. if using
native-tlssolves the issue then I will include that in the next release@Sorodon commented on GitHub (Aug 31, 2025):
This worked for me (even though the Device selection is (understandably) not working anymore).
Thanks a lot!
Should I keep the issue open since this seems just like a workaround or close it?
@arc-d3v commented on GitHub (Aug 31, 2025):
You should keep the issue open, spotify-player is still unusable as is until fix.
@TimVosch confirm that it is not working on
masteras well.@Sorodon commented on GitHub (Aug 31, 2025):
I suspect some other underlying cause there as it is working again for me. I did nothing other than uninstall from Pacman and install the
masterbranch via cargo.