v6.5.4
Fixes
-
A
401from the Spotify API on a token the session still considers valid no longer surfaces as a coordinator error: the account forces a token refresh and retries the call once. Spotify occasionally rejects a freshly refreshed token (Access token missing), which previously failed the whole update cycle:HTTP Error for GET to .../v1/me/player/devices returned 401 due to Access token missing Unexpected error fetching spotcast_... dataA
401means the request never executed, so the retry is safe for the playback writes too. If the rejection is ever caused by Spotcast rather than Spotify, the newSpotify rejected the access token for <url>warning makes it visible. -
The desktop session keeps its refresh token when Spotify omits
refresh_tokenfrom a refresh response. The response previously replaced the stored token wholesale, which would have left the session unable to refresh at all.
Full changelog: v6.5.3...v6.5.4