Failing CDN URLs cause no playback

Description If Spotify provides a broken CDN URL that returns an error HTTP response (e.g. HTTP code 530), the current version of librespot doesn't try fallback URLs and so all tracks will fail to play. There's a fix which is hopefully about to be merged in to librespot, so once it's merged, a new release of spotifyd will be needed to include it.

To Reproduce There are no steps to reproduce as it depends on Spotify providing a CDN URL which returns an error code. Some accounts have been recently receiving a 530 error from one CDN URL, but it can't be forced.

Expected behavior If a CDN URL is returning an HTTP error code, the other provided CDN URLs should be tried.

Logs

[ERROR] Unable to load encrypted file: Error { kind: FailedPrecondition, error: StatusCode(530) }
[ERROR] Skipping to next track, unable to load track <SpotifyUri("spotify:track:56lhDZNQ5J47aog6mGKeGk")>: ()

Compilation flags

• dbus_mpris
• alsa_backend
• portaudio_backend
• pulseaudio_backend
• rodio_backend

Versions (please complete the following information):

• OS: Ubuntu 24
• Spotifyd: 0.4.2

Additional context This is the PR in librespot that will fix the issue: https://github.com/librespot-org/librespot/pull/1722 Similar issues in other projects using librespot have also been reported. E.g. https://github.com/music-assistant/support/issues/5708