mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 17:35:50 +03:00
[GH-ISSUE #837] Error: initialize new Spotify session #504
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#504
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 @samuelstevens on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/837
Describe the bug
When running
spotify_playerI getError: initialize new Spotify session.To Reproduce
I have a recent, stock build of Chrome as my default browser. No extensions, no adblock, etc.
Expected behaviour
I expect to log in.
Log and backtrace
/Users/samstevens/.cache/spotify-player/spotify-player-25-09-21-14-42.backtracewas empty.Environment
cargo install spotify_player --locked@aome510 commented on GitHub (Sep 21, 2025):
Thanks for reporting. Based on the log and your issue description, I'm not sure why the
(Failed to parse server response)error happened (first time seeing this error). I just tried to authenticate again on my machine and it still works fine for me 🤔@samuelstevens commented on GitHub (Sep 22, 2025):
Just tried again with 0.21.1 and I have the same bug. I tried with
RUST_LOG=traceand got this log:I can provide additional details if possible.
@kabaskill commented on GitHub (Sep 22, 2025):
I had a similar issue where my session couldn't be created because of bad credentials. Then I noticed that my account is logged out from other instances (phone, pc etc.). Might be some account protection from Spotify because I've been using the CLI extensively since I discovered it.
However, after logging in again and deleting the cache of spotify-player, I was able log in again to the CLI. The cache of the CLI is kept here:
for reference, I built the app from source because fzf feature for the cargo version didn't work for me.
@stoicz commented on GitHub (Oct 22, 2025):
i had a similar issue, where i could not start the application because it was unable to init a new spotify session
rm -rf $HOME/.cache/spotify-player/*did the trick