spotify-tui icon indicating copy to clipboard operation
spotify-tui copied to clipboard

API response: convert result failed, progress_ms is negative instead of u32

Open Jojeee-xyz opened this issue 3 years ago • 6 comments

spotify-tui 0.25.0-1 spotifyd 0.3.2-1

When I launch `spt' and try to advance a track or change to a new song I'm getting this error. After pressing 'q' the problem goes away for a few songs and then starts happening again. If '^C' is used instead of 'q' the problem starts again straight after launching spotify-tui again. Not sure if this is something I've done or an issue with spt/spotifyd, etc.

Spotifyd_SPT_Issue

Jojeee-xyz avatar Sep 08 '21 09:09 Jojeee-xyz

Same here. It seems that progress_ms isn't always an unsigned integer. Maybe this part of the code

sofianedjerbi avatar Oct 03 '21 00:10 sofianedjerbi

Can confirm this. Although I noticed my system time was 10s in the future (checked with time.is). I did not enable ntp syncing on this relatively new system yet. Now that I have, I'll probably not run into this anymore. (I've only just now synced, so can't say quite yet.)

I guess to replicate, one could try setting system clock (way) in the future. Kind of weird that spotify is working with clock time though somewhere, and not relative time.

greenbigfrog avatar Oct 03 '21 12:10 greenbigfrog

As @greenbigfrog stated, synchronizing my system clock seems to fix the problem for me too! I checked the status of my system clock with timedatectl status and noted that "System clock synchronized: no" and "NTP service: inactive". Enabled NTP service by running timedatectl set-ntp true and it fixed the issue for me.

jkmingwen avatar Dec 02 '21 13:12 jkmingwen

I also got this issue, but spotifyd and spotify-tui are on the same computer, so in my case there is no time synchronization issue between the two. NTP is enabled anyway.

nim65s avatar Mar 31 '22 14:03 nim65s

Having the same issue but on windows terminal. Not sure what the equivalent timedatctl would be or if that is even the fix. Although it looks like it's been a few years since an update so maybe Spotify updated the api and that's causing the error now?

Edit: actually not getting the same exact error. Mine says Api response: convert result failed, reason: Error("unknown variant 'collection', expected artist, etc etc... line: 19, column: 25)

iAmThunderLIVE avatar Jul 29 '23 15:07 iAmThunderLIVE

Although it looks like it's been a few years since an update

:point_up: exactly.

https://github.com/aome510/spotify-player

apprehensions avatar Jul 29 '23 15:07 apprehensions