[GH-ISSUE #912] Api error: convert result failed, reason: Error("invalid value: integer -x, expected u32") #389

Open
opened 2026-02-28 14:48:51 +03:00 by kerem · 20 comments
Owner

Originally created by @prephyte on GitHub (Nov 8, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/912

I started getting this issue lately, which really bother me, although spt is still able to play music, but I hate looking at this screen every time I want to play something.
Here is the screenshot
image

P.S. afaik it tries to start song at negative point, and that fails. I tried reinstalling, checking my config, but had no luck with that. Thx in advance :)

Originally created by @prephyte on GitHub (Nov 8, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/912 I started getting this issue lately, which really bother me, although spt is still able to play music, but I hate looking at this screen every time I want to play something. Here is the screenshot ![image](https://user-images.githubusercontent.com/93487995/140795983-22dcd210-2c8f-4443-be9f-b16ba4d5f92d.png) P.S. afaik it tries to start song at negative point, and that fails. I tried reinstalling, checking my config, but had no luck with that. Thx in advance :)
Author
Owner

@rodneydup commented on GitHub (Nov 13, 2021):

I am getting this intermittently as well with spt 0.25.0 on Debian 11 with Gnome 38. When it happens, spt locks up by going back to this screen every time I press . I haven't found a pattern yet so I don't know what's causing it, but it didn't happen before I upgraded to 0.25.0.

<!-- gh-comment-id:968090870 --> @rodneydup commented on GitHub (Nov 13, 2021): I am getting this intermittently as well with spt 0.25.0 on Debian 11 with Gnome 38. When it happens, spt locks up by going back to this screen every time I press <esc>. I haven't found a pattern yet so I don't know what's causing it, but it didn't happen before I upgraded to 0.25.0.
Author
Owner

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

I'm getting this too. I think it's as simple as: spt expects the progress_ms field in this API response to return a positive integer (u32), but it's sometimes a negative number instead.

<!-- gh-comment-id:984317156 --> @icambron commented on GitHub (Dec 2, 2021): I'm getting this too. I think it's as simple as: `spt` expects the `progress_ms` field in this API response to return a positive integer (`u32`), but it's sometimes a negative number instead.
Author
Owner

@mikaelpr commented on GitHub (Dec 8, 2021):

There's also a relevant issue on spotifyd's page from over a year ago
https://github.com/Spotifyd/spotifyd/issues/665

Though it seems to have never been fixed client-side

<!-- gh-comment-id:988693076 --> @mikaelpr commented on GitHub (Dec 8, 2021): There's also a relevant issue on spotifyd's page from over a year ago https://github.com/Spotifyd/spotifyd/issues/665 Though it seems to have never been fixed client-side
Author
Owner

@Rigellute commented on GitHub (Dec 10, 2021):

Perhaps this has been fixed in rspotify (which handles deserializing the spotify API response).

I have been working on upgrading to the latest rspotify release (which has a number of breaking changes), but I don't have much time at the moment unfortunately.

<!-- gh-comment-id:990920854 --> @Rigellute commented on GitHub (Dec 10, 2021): Perhaps this has been fixed in rspotify (which handles deserializing the spotify API response). I have been working on upgrading to the latest rspotify release (which has a number of breaking changes), but I don't have much time at the moment unfortunately.
Author
Owner

@mikaelpr commented on GitHub (Dec 10, 2021):

Yeah, It appears that the fix for this was merged in September
https://github.com/ramsayleung/rspotify/pull/251/commits/d654f82475297399632c6fd5625c572dd20eb024

<!-- gh-comment-id:990933727 --> @mikaelpr commented on GitHub (Dec 10, 2021): Yeah, It appears that the fix for this was merged in September https://github.com/ramsayleung/rspotify/pull/251/commits/d654f82475297399632c6fd5625c572dd20eb024
Author
Owner

@marcelfoss commented on GitHub (Jan 14, 2022):

has anybody be able to fix this ugly error message at least from not being showed? or any idea to workaround?

<!-- gh-comment-id:1013449430 --> @marcelfoss commented on GitHub (Jan 14, 2022): has anybody be able to fix this ugly error message at least from not being showed? or any idea to workaround?
Author
Owner

@Raagh commented on GitHub (Mar 10, 2022):

I have also been experimenting the same, happens with every song

<!-- gh-comment-id:1063766394 --> @Raagh commented on GitHub (Mar 10, 2022): I have also been experimenting the same, happens with every song
Author
Owner

@B1T3X commented on GitHub (Mar 11, 2022):

Getting the same here only in my case it show that the unknown variant is "collection".
Tried compiling from source, snapping, and downloaded from the releases page. Nothing seems to work.
image

<!-- gh-comment-id:1065578920 --> @B1T3X commented on GitHub (Mar 11, 2022): Getting the same here only in my case it show that the unknown variant is "collection". Tried compiling from source, snapping, and downloaded from the releases page. Nothing seems to work. ![image](https://user-images.githubusercontent.com/61066934/157978546-f22e58f2-697d-41de-a22a-14e6465ddd96.png)
Author
Owner

@sewnie commented on GitHub (Mar 13, 2022):

Getting the same here only in my case it show that the unknown variant is "collection". Tried compiling from source, snapping, and downloaded from the releases page. Nothing seems to work.

see #960

<!-- gh-comment-id:1066060477 --> @sewnie commented on GitHub (Mar 13, 2022): > Getting the same here only in my case it show that the unknown variant is "collection". Tried compiling from source, snapping, and downloaded from the releases page. Nothing seems to work. see #960
Author
Owner

@sewnie commented on GitHub (Apr 7, 2022):

well ironically enough after seeing that get fixed now im getting this lol

<!-- gh-comment-id:1092073617 --> @sewnie commented on GitHub (Apr 7, 2022): well ironically enough after seeing that get fixed now im getting this lol
Author
Owner

@davidjrkim commented on GitHub (Jul 5, 2022):

still no updates?

<!-- gh-comment-id:1174714421 --> @davidjrkim commented on GitHub (Jul 5, 2022): still no updates?
Author
Owner

@sewnie commented on GitHub (Jul 5, 2022):

#1000
our only option is to wait for @Rigellute to have to rewrite most of the spotify-tui code to fit the new rspotify library update.

<!-- gh-comment-id:1174809097 --> @sewnie commented on GitHub (Jul 5, 2022): #1000 our only option is to wait for @Rigellute to have to rewrite most of the spotify-tui code to fit the new rspotify library update.
Author
Owner

@Mink5 commented on GitHub (Jul 28, 2022):

Also got this error when playing a new song.

<!-- gh-comment-id:1198714518 --> @Mink5 commented on GitHub (Jul 28, 2022): Also got this error when playing a new song.
Author
Owner

@harsha176 commented on GitHub (Jul 31, 2022):

+1

<!-- gh-comment-id:1200497971 --> @harsha176 commented on GitHub (Jul 31, 2022): +1
Author
Owner

@KyleTryon commented on GitHub (Oct 9, 2022):

Just installed from rust and seeing the same issue.

<!-- gh-comment-id:1272583516 --> @KyleTryon commented on GitHub (Oct 9, 2022): Just installed from rust and seeing the same issue.
Author
Owner

@katherineding commented on GitHub (Nov 7, 2022):

I was directed to here by #1021 (with the " unknown variant collection", not "progress_ms" negative" error). My system is Ubuntu 22.04, as Vanilla as it gets. The workaround for #1021 is as suggested in #964, to change around playlists until the error page goes away. But I haven't figured out if there's a specific type of playlist/collection that casues the problem. The error also seems to occur more when switching between playback devices.

<!-- gh-comment-id:1305004284 --> @katherineding commented on GitHub (Nov 7, 2022): I was directed to here by #1021 (with the " unknown variant collection", not "progress_ms" negative" error). My system is Ubuntu 22.04, as Vanilla as it gets. The workaround for #1021 is as suggested in #964, to change around playlists until the error page goes away. But I haven't figured out if there's a specific type of playlist/collection that casues the problem. The error also seems to occur more when switching between playback devices.
Author
Owner

@sewnie commented on GitHub (Nov 7, 2022):

this is taking forever to fix

<!-- gh-comment-id:1305905421 --> @sewnie commented on GitHub (Nov 7, 2022): this is taking forever to fix
Author
Owner

@jendahorak commented on GitHub (Jul 17, 2023):

same error on windows 10, would love the fix
obrazek

<!-- gh-comment-id:1638059437 --> @jendahorak commented on GitHub (Jul 17, 2023): same error on windows 10, would love the fix ![obrazek](https://github.com/Rigellute/spotify-tui/assets/70900705/669bdf62-98fe-4e9d-8df9-134ccdd56e3a)
Author
Owner

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

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

<!-- gh-comment-id:1638100167 --> @sewnie commented on GitHub (Jul 17, 2023): https://github.com/aome510/spotify-player
Author
Owner

@ericmckevitt commented on GitHub (Mar 2, 2024):

I'm having this issue when I search for an album. If the album is in my library, I can play it, but I can't search for it. I can search for songs, though, with no problem.

<!-- gh-comment-id:1974744614 --> @ericmckevitt commented on GitHub (Mar 2, 2024): I'm having this issue when I search for an album. If the album is in my library, I can play it, but I can't search for it. I can search for songs, though, with no problem.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#389
No description provided.