starred/spotify-tui

Fork 0

mirror of https://github.com/Rigellute/spotify-tui.git synced 2026-04-27 00:25:53 +03:00

[GH-ISSUE #883] API response: convert result failed, progress_ms is negative instead of u32 #375

New issue

Open

opened 2026-02-28 14:48:46 +03:00 by kerem · 6 comments

kerem commented

2026-02-28 14:48:46 +03:00

Owner

Originally created by @Jojeee-xyz on GitHub (Sep 8, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/883

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.

Originally created by @Jojeee-xyz on GitHub (Sep 8, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/883 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](https://user-images.githubusercontent.com/60971120/132479990-6426a6a0-ad40-4cbc-a95c-a3bba07873ff.png)

kerem commented

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

Author

Owner

@sofianedjerbi commented on GitHub (Oct 3, 2021):

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

@sofianedjerbi commented on GitHub (Oct 3, 2021): Same here. It seems that `progress_ms` isn't always an unsigned integer. Maybe [this part of the code](https://github.com/Rigellute/spotify-tui/blob/100feac945ba7a8dacc3414be40152cc4ba7c595/src/network.rs#L766)

kerem commented

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

Author

Owner

@greenbigfrog commented on GitHub (Oct 3, 2021):

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 commented on GitHub (Oct 3, 2021): Can confirm this. Although I noticed my system time was 10s in the future (checked with [time.is](https://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.

kerem commented

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

Author

Owner

@jkmingwen commented on GitHub (Dec 2, 2021):

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 commented on GitHub (Dec 2, 2021): 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.

kerem commented

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

Author

Owner

@nim65s commented on GitHub (Mar 31, 2022):

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 commented on GitHub (Mar 31, 2022): 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.

kerem commented

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

Author

Owner

@iAmThunderLIVE commented on GitHub (Jul 29, 2023):

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 commented on GitHub (Jul 29, 2023): 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)

kerem commented

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

Author

Owner

@sewnie commented on GitHub (Jul 29, 2023):

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

☝️ exactly.

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

@sewnie commented on GitHub (Jul 29, 2023): > Although it looks like it's been a few years since an update :point_up: exactly. https://github.com/aome510/spotify-player