mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #813] App launches but fails to load any data (playlists, albums, tracks) #1419
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#1419
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 @angelinuxx on GitHub (Aug 26, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/813
Describe the bug
The app launches correctly, but no data is loaded. Nothing can be fetched: playlists, albums, artists, liked songs, recently played, etc.
To Reproduce
Run spotify_player in the terminal.
Expected behaviour
Able to select and play tracks.
Log and backtrace
spotify-client*.backtrace
EMPTY
spotify-client*.log
Screenshots
Environment
--features image,daemonAdditional context
I have been using spotify_client since May 2025, and it worked perfectly until the last time I used it in late July.
I am also using a custom Spotify client_id for Spotify Connect, which previously worked without issues.
I updated to 0.20.7 today after noticing the problem (I also reverted to the default config and cleared the cache), but the issue had already occurred this morning on version 0.20.5.
@aome510 commented on GitHub (Aug 26, 2025):
See https://github.com/aome510/spotify-player/issues/802#issuecomment-3218342832
Can you try latest
maininstead?@angelinuxx commented on GitHub (Aug 27, 2025):
This solved the problem, thank you!
@JamesManningR commented on GitHub (Aug 27, 2025):
I still get this error with the newest version of main
Tried
Log
@aome510 commented on GitHub (Aug 27, 2025):
The log doesn't indicate you run the latest
main. How did you run it? Please make sure the binary is correct (is the one built by latestmain) not the old binary you installed previously