Nick Steel

Debug log please. I cannot reproduce this.

Is this with all tracks? Does switching to a different album make any difference? What about selecting different `--bitrate`? Just to double check, you do have premium, yes? Is this...

When Spotify change things they do it on a handful of accounts at a time. They may be phasing out this way of getting the key and you're unlucky enough...

Here's my debug log. Very similar... except it can get the key and play audio like normal. So not much insight there, just to show everything is the same... right...

I don't think so because that was discovered by comparing the difference in behaviour between go-librespot and librespot as per https://github.com/devgianlu/go-librespot/issues/235#issuecomment-3599449993. And the above working log I provided replicates exactly...

@Josh-00FF00 have you seen the [BufferSink](https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/blob/main/audio/spotify/src/spotifyaudiosrc/imp.rs?ref_type=heads#L294) used in [spotifyaudiosrc](https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/blob/main/audio/spotify/src/spotifyaudiosrc/imp.rs?ref_type=heads#L406-430)? Might that method work for you?

Are you using etags when refreshing your cached data? Saves a lot of traffic and deserialisation work which speeds things up. In Mopidy-Spotify I found that a big (background) cache...

Sorry, no, I don't actually use psst. I'm just lurking in projects that implement Spotify streaming.

Have you looked at https://github.com/rustyhorde/vergen/ ? I think it leaves a placeholder in the values when they are unavailable due to missing git dir.

Please create a separate feature request for this (assuming there isn't one already), rather than hijacking this very old bug report. Thanks.