[GH-ISSUE #437] Use upstream rspotify (not my fork) #182

New issue

Closed

opened 2026-02-28 14:47:36 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 14:47:36 +03:00

Owner

Originally created by @Rigellute on GitHub (May 4, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/437

Due to changes on Spotify's end, the audio analysis endpoint has started returning missing attributes which aren't expected when deserializing (causing a crash).

A temporary fix is to use my fork of rspotify that makes all audio analysis properties optional.

Hopefully the Spotify API will clarify which properties are now optional so we can update rspotify to fix this properly.

One problem with using my fork is that crates.io won't accept a git dependency. So this is bodge fix.

Originally created by @Rigellute on GitHub (May 4, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/437 Due to changes on Spotify's end, the audio analysis endpoint has started returning missing attributes which aren't expected when deserializing (causing a crash). A temporary fix is to use my fork of rspotify that makes all audio analysis properties optional. Hopefully the Spotify API will clarify which properties are now optional so we can update rspotify to fix this properly. One problem with using my fork is that crates.io won't accept a `git` dependency. So this is bodge fix.