Spotify API Change: Audio key issue

[LowerHater]

Compatible Device

• I'm running Raspotify on a compatible Device

Are you sure?

• I'm not trying to run Raspotify on a ARMv6 device

Compatible OS

• I'm running Raspotify on a compatible OS

Compatible Configuration

• I'm running Raspotify on a compatible Configuration

Latest Version

• I'm running the latest version of Raspotify

Are you sure?

• I'm not running Raspotify 0.31.8.1 on a Pi v1 or Pi Zero

Due Diligence

• I have done my due diligence

What happened?

Just a note that all Librespot dependent projects seem to be affected by the Spotify API/Authentication changes; with Librespot existing method no longer viable.

Spotty, which uses michaelherger's librespot fork; was able to use a custom OAuth fix, to update and resolved this:

Announce: Spotty v4.60.0 (the Christmas Crash Release

Posting here, so if this is actively worked on; users can subscribe and track activity.

Happy holidays.

Relevant log output and/or the contents of /etc/raspotify/crash_report if any ( sudo journalctl -u raspotify -b and sudo cat /etc/raspotify/crash_report )

[23:28:01.166] I MercurySession.cpp:42: Received packet, command: 178
[23:28:01.166] D MercurySession.cpp:174: Received mercury packet
[23:28:01.166] I TrackQueue.cpp:162: Track name: Top Jimmy - 2015 Remaster
[23:28:01.167] I TrackQueue.cpp:163: Track duration: 179906
[23:28:01.167] D TrackQueue.cpp:165: trackInfo.restriction.size() = 1
[23:28:01.167] D TrackQueue.cpp:216: File format: 2
[23:28:01.167] D TrackQueue.cpp:216: File format: 1
[23:28:01.249] I MercurySession.cpp:42: Received packet, command: 14
[23:28:01.249] E TrackQueue.cpp:262: Failed to get audio key
[23:28:01.250] E TrackPlayer.cpp:165: Track failed to load, skipping it

[olm52]

I confirm this problem

[kimtore]

If I understand correctly, this issue is now upstream: librespot-org/librespot#1649

@LowerHater: does it look like the same problem?

[jleoj]

If I understand correctly, this issue is now upstream: librespot-org/librespot#1649

@LowerHater: does it look like the same problem?

Yes it is

[HeyMeco]

I have a feeling this time spotify will deprecate the librespot auth methods...
Hopefully they find a solution

[github-actions]

This issue has been marked as stale. It will closed in 7 days if there is no activity.

[kimtore]

Unfortunately there hasn't been any commits in the librespot repository for a few months. As I understand, a solution exists, but not through legal methods, i.e. Spotify will pursue with legal action if the solution is published.

Not sure what to make of this, except that there are many physical devices that uses Spotify Connect that will not get patches, so I hope that they will keep this endpoint open forever to keep them running.

My personal recommendation is to set up the daemon in unauthenticated mode, it is working pretty well for me at least.

[github-actions]

This issue has been marked as stale. It will closed in 7 days if there is no activity.