Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Jojeee-xyz opened this issue Sep 8, 2021 · 6 comments

Comments

@Jojeee-xyz
Copy link

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

@chaoxel
Copy link

chaoxel commented Oct 3, 2021

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

@greenbigfrog
Copy link

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.

@jkmingwen
Copy link

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.

@nim65s
Copy link

nim65s commented 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.

@iAmThunderLIVE
Copy link

iAmThunderLIVE commented 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)

@apprehensions
Copy link

apprehensions commented Jul 29, 2023

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

☝️ exactly.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants