[GH-ISSUE #1625] Stopped working again - another change on Spotify's side? #741

Closed
opened 2026-02-27 19:32:13 +03:00 by kerem · 3 comments
Owner

Originally created by @sixtyfive on GitHub (Nov 8, 2025).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1625

Unfortunately, I'm getting the deaded skipping to next track, unable to load track again. I revisited #1623 / #1622 but this time, found nothing in there that helped. Log looks like this:

2025-11-08 11-45-04.230 [Info] (librespot_core::session) Connecting to AP "ap-gew4.spotify.com:4070"
2025-11-08 11-45-04.402 [Info] (librespot_core::session) Authenticated as 'xxx' !
2025-11-08 11-45-04.403 [Info] (librespot_core::session) Country: "DE"
2025-11-08 11-45-04.868 [Info] (librespot_core::spclient) Resolved "gew4-spclient.spotify.com:443" as spclient access point
2025-11-08 11-45-04.990 [Info] (librespot_connect::spirc) active device is <> with session <9095ff77d36abef33a72769cba765656>
2025-11-08 11-45-05.137 [Warn] (librespot_connect::state::context) couldn't load context info because: context is not available. type: Default
2025-11-08 11-45-05.316 [Error] (librespot_playback::player) Track should be available, but no alternatives found.
2025-11-08 11-45-05.317 [Warn] (librespot_playback::player) <spotify:track:23LviCU62XnXrtVuFDPjgZ> is not available
2025-11-08 11-45-05.317 [Error] (librespot_playback::player) Skipping to next track, unable to load track <SpotifyId("spotify:track:23LviCU62XnXrtVuFDPjgZ")>: ()
2025-11-08 11-45-05.317 [Error] (librespot_connect::spirc) could not dispatch player event: Invalid state { context is not available. type: Default }

I'll happily provide any extra info if you let me know what you need!

Originally created by @sixtyfive on GitHub (Nov 8, 2025). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1625 Unfortunately, I'm getting the deaded `skipping to next track, unable to load track again`. I revisited #1623 / #1622 but this time, found nothing in there that helped. Log looks like this: ``` 2025-11-08 11-45-04.230 [Info] (librespot_core::session) Connecting to AP "ap-gew4.spotify.com:4070" 2025-11-08 11-45-04.402 [Info] (librespot_core::session) Authenticated as 'xxx' ! 2025-11-08 11-45-04.403 [Info] (librespot_core::session) Country: "DE" 2025-11-08 11-45-04.868 [Info] (librespot_core::spclient) Resolved "gew4-spclient.spotify.com:443" as spclient access point 2025-11-08 11-45-04.990 [Info] (librespot_connect::spirc) active device is <> with session <9095ff77d36abef33a72769cba765656> 2025-11-08 11-45-05.137 [Warn] (librespot_connect::state::context) couldn't load context info because: context is not available. type: Default 2025-11-08 11-45-05.316 [Error] (librespot_playback::player) Track should be available, but no alternatives found. 2025-11-08 11-45-05.317 [Warn] (librespot_playback::player) <spotify:track:23LviCU62XnXrtVuFDPjgZ> is not available 2025-11-08 11-45-05.317 [Error] (librespot_playback::player) Skipping to next track, unable to load track <SpotifyId("spotify:track:23LviCU62XnXrtVuFDPjgZ")>: () 2025-11-08 11-45-05.317 [Error] (librespot_connect::spirc) could not dispatch player event: Invalid state { context is not available. type: Default } ``` I'll happily provide any extra info if you let me know what you need!
kerem 2026-02-27 19:32:13 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@photovoltex commented on GitHub (Nov 8, 2025):

Why did you ignore the issue template? If you hadn't we would probably see that you are not using a development build and rather a published version in which this isn't fixed, yet. The bug is only resolved on the current dev branch and will be fixed in an published version with the upcoming 0.8 release.

Please provide the version your are using or alternatively the start of the log where the version is displayed.

<!-- gh-comment-id:3506441775 --> @photovoltex commented on GitHub (Nov 8, 2025): Why did you ignore the issue template? If you hadn't we would probably see that you are not using a development build and rather a published version in which this isn't fixed, yet. The bug is only resolved on the current `dev` branch and will be fixed in an published version with the upcoming 0.8 release. Please provide the version your are using or alternatively the start of the log where the version is displayed.
Author
Owner

@kingosticks commented on GitHub (Nov 8, 2025):

Let's reopen if this is updated with anything interesting and useful.

<!-- gh-comment-id:3506486099 --> @kingosticks commented on GitHub (Nov 8, 2025): Let's reopen if this is updated with anything interesting and useful.
Author
Owner

@sixtyfive commented on GitHub (Nov 8, 2025):

I apologize - it was not my intention to upset anyone by removing the template. I felt a little overwhelmed by it and was so sure something must have been changed by Spotify that the template didn't seem relevant.

Indeed, the librespot version included in the ghcr.io/firefrei/snapcast/server:latest Docker build is 0.7.1 987dfa5 ("Built on 2025-11-01") only. I shall do my own build now instead. Apologies again and thank you for explaining the situation!

<!-- gh-comment-id:3506523909 --> @sixtyfive commented on GitHub (Nov 8, 2025): I apologize - it was not my intention to upset anyone by removing the template. I felt a little overwhelmed by it and was so sure something must have been changed by Spotify that the template didn't seem relevant. Indeed, the librespot version included in the `ghcr.io/firefrei/snapcast/server:latest` Docker build is 0.7.1 987dfa5 ("Built on 2025-11-01") only. I shall do my own build now instead. Apologies again and thank you for explaining the situation!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#741
No description provided.