starred/rspotify
1
0
Fork 0
mirror of https://github.com/ramsayleung/rspotify.git synced 2026-04-25 23:45:52 +03:00
Code Issues 15 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #452] json parse error when calling artist method #150

New issue
Closed
opened 2026-02-27 20:23:24 +03:00 by kerem · 24 comments
kerem commented 2026-02-27 20:23:24 +03:00
Owner
Copy link

Originally created by @aome510 on GitHub (Jan 6, 2024).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/452

Describe the bug
Client now returns

Bad request: json parse error: invalid type: floating point `49022656`, expected u32 at line 1 column 130: invalid type: floating point `49022656`, expected u32 at line 1 column 130

for every artist request. The reason seems to be because Spotify changes the type of followers.total and other fields to float.

To Reproduce
Steps to reproduce the behavior:

  1. Run
curl --request GET \
        --url https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d \
        --header 'Authorization: Bearer $TOKEN'
  1. Observe that follower.total is not an integer. Example result:
{"external_urls":{"spotify":"https://open.spotify.com/artist/1dfeR4HaWDbWqFHLkxsg1d"},"followers":{"href":null,"total":4.9022656E7},"genres":["classic rock","glam rock","rock"],"href":"https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d","id":"1dfeR4HaWDbWqFHLkxsg1d","images":[{"url":"https://i.scdn.co/image/b040846ceba13c3e9c125d68389491094e7f2982","height":806.0,"width":999.0},{"url":"https://i.scdn.co/image/af2b8e57f6d7b5d43a616bd1e27ba552cd8bfd42","height":516.0,"width":640.0},{"url":"https://i.scdn.co/image/c06971e9ff81696699b829484e3be165f4e64368","height":161.0,"width":200.0},{"url":"https://i.scdn.co/image/6dd0ffd270903d1884edf9058c49f58b03db893d","height":52.0,"width":64.0}],"name":"Queen","popularity":84.0,"type":"artist","uri":"spotify:artist:1dfeR4HaWDbWqFHLkxsg1d"}
  1. Notice that some fields' type are changed to float such as followers.total, popularity
Originally created by @aome510 on GitHub (Jan 6, 2024). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/452 **Describe the bug** Client now returns ``` Bad request: json parse error: invalid type: floating point `49022656`, expected u32 at line 1 column 130: invalid type: floating point `49022656`, expected u32 at line 1 column 130 ``` for every [`artist`](https://docs.rs/rspotify/latest/rspotify/clients/trait.BaseClient.html#method.artist) request. The reason seems to be because Spotify changes the type of `followers.total` and other fields to float. **To Reproduce** Steps to reproduce the behavior: 1. Run ```shell curl --request GET \ --url https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d \ --header 'Authorization: Bearer $TOKEN' ``` 2. Observe that `follower.total` is not an integer. Example result: ``` {"external_urls":{"spotify":"https://open.spotify.com/artist/1dfeR4HaWDbWqFHLkxsg1d"},"followers":{"href":null,"total":4.9022656E7},"genres":["classic rock","glam rock","rock"],"href":"https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d","id":"1dfeR4HaWDbWqFHLkxsg1d","images":[{"url":"https://i.scdn.co/image/b040846ceba13c3e9c125d68389491094e7f2982","height":806.0,"width":999.0},{"url":"https://i.scdn.co/image/af2b8e57f6d7b5d43a616bd1e27ba552cd8bfd42","height":516.0,"width":640.0},{"url":"https://i.scdn.co/image/c06971e9ff81696699b829484e3be165f4e64368","height":161.0,"width":200.0},{"url":"https://i.scdn.co/image/6dd0ffd270903d1884edf9058c49f58b03db893d","height":52.0,"width":64.0}],"name":"Queen","popularity":84.0,"type":"artist","uri":"spotify:artist:1dfeR4HaWDbWqFHLkxsg1d"} ``` 3. Notice that some fields' type are changed to float such as `followers.total`, `popularity`
kerem 2026-02-27 20:23:24 +03:00
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 6, 2024):

It's weird that the total and popularity are marked as integer in their official document, but actually return float data.

I tried to reproduce this bug by following your instruction in the document console, but the response is different from yours.

curl --request GET \
  --url https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d \
  --header 'Authorization: Bearer $TOKEN'

{
  "external_urls": {
    "spotify": "https://open.spotify.com/artist/1dfeR4HaWDbWqFHLkxsg1d"
  },
  "followers": {
    "href": null,
    "total": 49022656
  },
  "genres": ["classic rock", "glam rock", "rock"],
  "href": "https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d?locale=en-US%2Cen%3Bq%3D0.9%2Czh-CN%3Bq%3D0.8%2Czh%3Bq%3D0.7",
  "id": "1dfeR4HaWDbWqFHLkxsg1d",
  "images": [
    {
      "url": "https://i.scdn.co/image/b040846ceba13c3e9c125d68389491094e7f2982",
      "height": 806,
      "width": 999
    },
    {
      "url": "https://i.scdn.co/image/af2b8e57f6d7b5d43a616bd1e27ba552cd8bfd42",
      "height": 516,
      "width": 640
    },
    {
      "url": "https://i.scdn.co/image/c06971e9ff81696699b829484e3be165f4e64368",
      "height": 161,
      "width": 200
    },
    {
      "url": "https://i.scdn.co/image/6dd0ffd270903d1884edf9058c49f58b03db893d",
      "height": 52,
      "width": 64
    }
  ],
  "name": "Queen",
  "popularity": 84,
  "type": "artist",
  "uri": "spotify:artist:1dfeR4HaWDbWqFHLkxsg1d"
}

followers.total, popularity are both integer rather than float.

<!-- gh-comment-id:1879745717 --> @ramsayleung commented on GitHub (Jan 6, 2024): It's weird that the total and popularity are marked as integer in their [official document](https://developer.spotify.com/documentation/web-api/reference/get-an-artist), but actually return float data. I tried to reproduce this bug by following your instruction in the [document console](https://developer.spotify.com/documentation/web-api/reference/get-an-artist), but the response is different from yours. ```sh curl --request GET \ --url https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d \ --header 'Authorization: Bearer $TOKEN' ``` ```json { "external_urls": { "spotify": "https://open.spotify.com/artist/1dfeR4HaWDbWqFHLkxsg1d" }, "followers": { "href": null, "total": 49022656 }, "genres": ["classic rock", "glam rock", "rock"], "href": "https://api.spotify.com/v1/artists/1dfeR4HaWDbWqFHLkxsg1d?locale=en-US%2Cen%3Bq%3D0.9%2Czh-CN%3Bq%3D0.8%2Czh%3Bq%3D0.7", "id": "1dfeR4HaWDbWqFHLkxsg1d", "images": [ { "url": "https://i.scdn.co/image/b040846ceba13c3e9c125d68389491094e7f2982", "height": 806, "width": 999 }, { "url": "https://i.scdn.co/image/af2b8e57f6d7b5d43a616bd1e27ba552cd8bfd42", "height": 516, "width": 640 }, { "url": "https://i.scdn.co/image/c06971e9ff81696699b829484e3be165f4e64368", "height": 161, "width": 200 }, { "url": "https://i.scdn.co/image/6dd0ffd270903d1884edf9058c49f58b03db893d", "height": 52, "width": 64 } ], "name": "Queen", "popularity": 84, "type": "artist", "uri": "spotify:artist:1dfeR4HaWDbWqFHLkxsg1d" } ``` `followers.total`, `popularity` are both integer rather than float.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@maplefluff commented on GitHub (Jan 6, 2024):

im getting this same error too, think spotify may have changed something because this was all fine yesterday
response from curl:

{
	"external_urls": {
		"spotify": "https://open.spotify.com/artist/4bwIf0yXJf0F9AmOl2J78M"
	},
	"followers": {
		"href": null,
		"total": 194172.0
	},
	"genres": [
		"denpa-kei",
		"rhythm game"
	],
	"href": "https://api.spotify.com/v1/artists/4bwIf0yXJf0F9AmOl2J78M",
	"id": "4bwIf0yXJf0F9AmOl2J78M",
	"images": [
		{
			"url": "https://i.scdn.co/image/ab6761610000e5ebc1f9dd30f82038e91e865d82",
			"height": 640.0,
			"width": 640.0
		},
		{
			"url": "https://i.scdn.co/image/ab67616100005174c1f9dd30f82038e91e865d82",
			"height": 320.0,
			"width": 320.0
		},
		{
			"url": "https://i.scdn.co/image/ab6761610000f178c1f9dd30f82038e91e865d82",
			"height": 160.0,
			"width": 160.0
		}
	],
	"name": "Camellia",
	"popularity": 51.0,
	"type": "artist",
	"uri": "spotify:artist:4bwIf0yXJf0F9AmOl2J78M"
}```
<!-- gh-comment-id:1879757000 --> @maplefluff commented on GitHub (Jan 6, 2024): im getting this same error too, think spotify may have changed something because this was all fine yesterday response from curl: ```json { "external_urls": { "spotify": "https://open.spotify.com/artist/4bwIf0yXJf0F9AmOl2J78M" }, "followers": { "href": null, "total": 194172.0 }, "genres": [ "denpa-kei", "rhythm game" ], "href": "https://api.spotify.com/v1/artists/4bwIf0yXJf0F9AmOl2J78M", "id": "4bwIf0yXJf0F9AmOl2J78M", "images": [ { "url": "https://i.scdn.co/image/ab6761610000e5ebc1f9dd30f82038e91e865d82", "height": 640.0, "width": 640.0 }, { "url": "https://i.scdn.co/image/ab67616100005174c1f9dd30f82038e91e865d82", "height": 320.0, "width": 320.0 }, { "url": "https://i.scdn.co/image/ab6761610000f178c1f9dd30f82038e91e865d82", "height": 160.0, "width": 160.0 } ], "name": "Camellia", "popularity": 51.0, "type": "artist", "uri": "spotify:artist:4bwIf0yXJf0F9AmOl2J78M" }```
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 6, 2024):

Yes, I can reproduce your problem now, I've submitted a ticket to Spotify to ask for clarity: https://community.spotify.com/t5/Spotify-for-Developers/The-response-type-of-artist-endpoint-is-marked-as-Integer-in/m-p/5800044

<!-- gh-comment-id:1879821894 --> @ramsayleung commented on GitHub (Jan 6, 2024): Yes, I can reproduce your problem now, I've submitted a ticket to Spotify to ask for clarity: https://community.spotify.com/t5/Spotify-for-Developers/The-response-type-of-artist-endpoint-is-marked-as-Integer-in/m-p/5800044
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@gansheer commented on GitHub (Jan 6, 2024):

Hi @ramsayleung, just so you know there is an error in the issue link https://github.com/ramsayleung/rspotify/issues/452m (trailing m) in your Spotify ticket.

<!-- gh-comment-id:1879827392 --> @gansheer commented on GitHub (Jan 6, 2024): Hi @ramsayleung, just so you know there is an error in the issue link `https://github.com/ramsayleung/rspotify/issues/452m` (trailing **m**) in your Spotify ticket.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 6, 2024):

Thanks for your heads-up, I've revised the link to the correct one. But it's odd that a developer replied in the ticket saying what he got with curl was integer data instead of float data.

Unfortunately, this ticket is marked as spam...

I've submitted an abuse report.

<!-- gh-comment-id:1879842498 --> @ramsayleung commented on GitHub (Jan 6, 2024): Thanks for your heads-up, I've revised the link to the correct one. But it's odd that a developer replied in the ticket saying what he got with `curl` was integer data instead of float data. Unfortunately, this ticket is marked as spam... I've submitted an abuse report.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@PMARZV commented on GitHub (Jan 6, 2024):

Hey here! Developing an app for android and i have the same problem with the GETARTISTS endpoint

<!-- gh-comment-id:1879870371 --> @PMARZV commented on GitHub (Jan 6, 2024): Hey here! Developing an app for android and i have the same problem with the GETARTISTS endpoint
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Jan 20, 2024):

I don't think Spotify will give their response anytime soon. I wonder if we have any plans to mitigate this issue @ramsayleung ?

<!-- gh-comment-id:1902248084 --> @aome510 commented on GitHub (Jan 20, 2024): I don't think Spotify will give their response anytime soon. I wonder if we have any plans to mitigate this issue @ramsayleung ?
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 23, 2024):

One of the workarounds comes to my mind is converting the Integer type to float type to bypass the issue. But in my perspective, I don't think it's a great idea because

  1. The SDK shouldn't silently swallow the bug caused by the Spotify server side, a better solution will be prompting the issue to Spotify and push them to fix the problem
  2. It will introduce a breaking change in this library, which's definitely unnecessary and avoidable.

I personally prefer to keep escalating and making "noise" to the Spotify developers, the louder noise we could make, the higher probability the Spotify team could be aware of this problem and fix it.

<!-- gh-comment-id:1905228395 --> @ramsayleung commented on GitHub (Jan 23, 2024): One of the workarounds comes to my mind is converting the Integer type to float type to bypass the issue. But in my perspective, I don't think it's a great idea because 1. The SDK shouldn't silently swallow the bug caused by the Spotify server side, a better solution will be prompting the issue to Spotify and push them to fix the problem 2. It will introduce a breaking change in this library, which's definitely unnecessary and avoidable. I personally prefer to keep escalating and **making "noise"** to the Spotify developers, the louder noise we could make, the higher probability the Spotify team could be aware of this problem and fix it.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 23, 2024):

I've sent a message to escalate this issue to the Spotify team via this link: https://support.spotify.com/ca-en/contact-spotify-support/, here is the response from their associate:

I already forward this issue to the team backstage. Also, the tech folks backstage confirm that they're already ahead of this and currently working for a fix. No need to worry now :)

Also, our Tech folks are known for their hard work so this will be fixed in no time! Consider this issue resolved.

<!-- gh-comment-id:1905245064 --> @ramsayleung commented on GitHub (Jan 23, 2024): I've sent a message to escalate this issue to the Spotify team via this link: https://support.spotify.com/ca-en/contact-spotify-support/, here is the response from their associate: > I already forward this issue to the team backstage. Also, the tech folks backstage confirm that they're already ahead of this and currently working for a fix. No need to worry now :) > Also, our Tech folks are known for their hard work so this will be fixed in no time! Consider this issue resolved.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Jan 23, 2024):

I've sent a message to escalate this issue to the Spotify team via this link: https://support.spotify.com/ca-en/contact-spotify-support/, here is the response from their associate:

I already forward this issue to the team backstage. Also, the tech folks backstage confirm that they're already ahead of this and currently working for a fix. No need to worry now :)

Also, our Tech folks are known for their hard work so this will be fixed in no time! Consider this issue resolved.

Great! Thank you @ramsayleung

<!-- gh-comment-id:1905247749 --> @aome510 commented on GitHub (Jan 23, 2024): > I've sent a message to escalate this issue to the Spotify team via this link: https://support.spotify.com/ca-en/contact-spotify-support/, here is the response from their associate: > > > I already forward this issue to the team backstage. Also, the tech folks backstage confirm that they're already ahead of this and currently working for a fix. No need to worry now :) > > > Also, our Tech folks are known for their hard work so this will be fixed in no time! Consider this issue resolved. Great! Thank you @ramsayleung
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@grantshandy commented on GitHub (Jan 29, 2024):

This issue is also holding up the development of a project of mine. If it isn't fixed soon by the spotify developers would rspotify support deserializing all u32 fields with a custom Deserializer a la #[serde(deserialize_with = "as_u32")]? as_u32 would automatically convert float fields into int ones and keep the same default behavior as before. It's pretty hacky, but it would fix the issue for now/if it arises again (im feeling pretty pessimistic lol). It'd be a less permissive version of serde-this-or-that's as_u64.

This solution wouldn't introduce breaking changes in the API as @ramsayleung pointed out, and the fix would continue to work if spotify does get around to fixing the issue. Plus, it would only have the overhead of converting any given f64 to a u32. If there's any interest in this sort of fix, let me know and I can open up a PR pretty quick.

<!-- gh-comment-id:1915189196 --> @grantshandy commented on GitHub (Jan 29, 2024): This issue is also holding up the development of a project of mine. If it isn't fixed soon by the spotify developers would rspotify support deserializing all `u32` fields with a custom `Deserializer` a la `#[serde(deserialize_with = "as_u32")]`? `as_u32` would automatically convert float fields into int ones and keep the same default behavior as before. It's pretty hacky, but it would fix the issue for now/if it arises again (im feeling pretty pessimistic lol). It'd be a less permissive version of `serde-this-or-that`'s [`as_u64`](https://docs.rs/serde-this-or-that/latest/serde_this_or_that/fn.as_u64.html). This solution wouldn't introduce breaking changes in the API as @ramsayleung pointed out, and the fix would continue to work if spotify does get around to fixing the issue. Plus, it would only have the overhead of converting any given `f64` to a `u32`. If there's any interest in this sort of fix, let me know and I can open up a PR pretty quick.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@maplefluff commented on GitHub (Jan 29, 2024):

This issue is also holding up the development of a project of mine. If it isn't fixed soon by the spotify developers would rspotify support deserializing all u32 fields with a custom Deserializer a la #[serde(deserialize_with = "as_u32")]? as_u32 would automatically convert float fields into int ones and keep the same default behavior as before. It's pretty hacky, but it would fix the issue for now/if it arises again (im feeling pretty pessimistic lol). It'd be a less permissive version of serde-this-or-that's as_u64.

This solution wouldn't introduce breaking changes in the API as @ramsayleung pointed out, and the fix would continue to work if spotify does get around to fixing the issue. Plus, it would only have the overhead of converting any given f64 to a u32. If there's any interest in this sort of fix, let me know and I can open up a PR pretty quick.

One thing you could do as a temporary workaround is this

        match rspotify
            .api_get(&format!("artists/{}", artist_id), &Query::new())
            .await
        {
            Ok(artist) => {
                // Manually parse the json for now
                let artist_json: Result<Value, _> = serde_json::from_str(&artist);
                match artist_json {
                }
        }
        ```
        im not sure if its the bestt way but its what im using for now and it seems to work alright, still learning stuff lol
        but it stopped me from needing to halt development on my stuff temporarily
<!-- gh-comment-id:1915256043 --> @maplefluff commented on GitHub (Jan 29, 2024): > This issue is also holding up the development of a project of mine. If it isn't fixed soon by the spotify developers would rspotify support deserializing all `u32` fields with a custom `Deserializer` a la `#[serde(deserialize_with = "as_u32")]`? `as_u32` would automatically convert float fields into int ones and keep the same default behavior as before. It's pretty hacky, but it would fix the issue for now/if it arises again (im feeling pretty pessimistic lol). It'd be a less permissive version of `serde-this-or-that`'s [`as_u64`](https://docs.rs/serde-this-or-that/latest/serde_this_or_that/fn.as_u64.html). > > This solution wouldn't introduce breaking changes in the API as @ramsayleung pointed out, and the fix would continue to work if spotify does get around to fixing the issue. Plus, it would only have the overhead of converting any given `f64` to a `u32`. If there's any interest in this sort of fix, let me know and I can open up a PR pretty quick. One thing you could do as a temporary workaround is this ```rs match rspotify .api_get(&format!("artists/{}", artist_id), &Query::new()) .await { Ok(artist) => { // Manually parse the json for now let artist_json: Result<Value, _> = serde_json::from_str(&artist); match artist_json { } } ``` im not sure if its the bestt way but its what im using for now and it seems to work alright, still learning stuff lol but it stopped me from needing to halt development on my stuff temporarily
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 30, 2024):

One thing you could do as a temporary workaround is this

But this temporary workaround only for the you, the sole developer who decides to engage this approach.

I would try to implement the as_u32 approach without imposing breaking change as a short term solution, as we actually don't know when will Spotify fix this issue.

<!-- gh-comment-id:1916001278 --> @ramsayleung commented on GitHub (Jan 30, 2024): > One thing you could do as a temporary workaround is this But this temporary workaround only for the **you**, the sole developer who decides to engage this approach. I would try to implement the `as_u32` approach without imposing breaking change as a short term solution, as we actually don't know when will Spotify fix this issue.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@grantshandy commented on GitHub (Jan 30, 2024):

Should I contribute the fix? I can do it in the next two days unless you'd like to implement it yourself.

<!-- gh-comment-id:1916038641 --> @grantshandy commented on GitHub (Jan 30, 2024): Should I contribute the fix? I can do it in the next two days unless you'd like to implement it yourself.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Jan 30, 2024):

I could provide the code snippet for your reference, feel free to contribute and issue a PR :)

pub mod data_type_patcher {
    use serde::{Deserialize, Deserializer};
    pub fn as_u32<'de, D>(deserializer: D) -> Result<u32, D::Error>
where
    D: Deserializer<'de>,
{
    let float_data: f64 = Deserialize::deserialize(deserializer)?;

    let u32_data = float_data as u32;

    Ok(u32_data)
}
}
<!-- gh-comment-id:1916042555 --> @ramsayleung commented on GitHub (Jan 30, 2024): I could provide the code snippet for your reference, feel free to contribute and issue a PR :) ``` rust pub mod data_type_patcher { use serde::{Deserialize, Deserializer}; pub fn as_u32<'de, D>(deserializer: D) -> Result<u32, D::Error> where D: Deserializer<'de>, { let float_data: f64 = Deserialize::deserialize(deserializer)?; let u32_data = float_data as u32; Ok(u32_data) } } ```
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@m-torhan commented on GitHub (Feb 1, 2024):

As I didn't see any PR related to this I let myself to implement it https://github.com/ramsayleung/rspotify/pull/457.

I tested it with https://github.com/aome510/spotify-player and it worked well.

<!-- gh-comment-id:1920934527 --> @m-torhan commented on GitHub (Feb 1, 2024): As I didn't see any PR related to this I let myself to implement it https://github.com/ramsayleung/rspotify/pull/457. I tested it with https://github.com/aome510/spotify-player and it worked well.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 3, 2024):

Look like a workaround patch landed to master. @ramsayleung do you have any plans to release a new version?

<!-- gh-comment-id:1925408250 --> @aome510 commented on GitHub (Feb 3, 2024): Look like a workaround patch landed to `master`. @ramsayleung do you have any plans to release a new version?
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Feb 9, 2024):

I am on vacation right now, I will release a new version when I am back :)

On Sun, Feb 4, 2024 at 1:34 AM Thang Pham @.***> wrote:

Look like a workaround patch landed to master. @ramsayleung
https://github.com/ramsayleung do you have any plans to release a new
version?

—
Reply to this email directly, view it on GitHub
https://github.com/ramsayleung/rspotify/issues/452#issuecomment-1925408250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADMGCSMC32AKD5FDO26MFZ3YRZYLXAVCNFSM6AAAAABBPP63O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGQYDQMRVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:1935261393 --> @ramsayleung commented on GitHub (Feb 9, 2024): I am on vacation right now, I will release a new version when I am back :) On Sun, Feb 4, 2024 at 1:34 AM Thang Pham ***@***.***> wrote: > Look like a workaround patch landed to master. @ramsayleung > <https://github.com/ramsayleung> do you have any plans to release a new > version? > > — > Reply to this email directly, view it on GitHub > <https://github.com/ramsayleung/rspotify/issues/452#issuecomment-1925408250>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADMGCSMC32AKD5FDO26MFZ3YRZYLXAVCNFSM6AAAAABBPP63O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGQYDQMRVGA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

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

I'm now getting the same error but with get-several-tracks API call. To reproduce, run

curl --request GET \
         --url "https://api.spotify.com/v1/tracks?ids=5O2P9iiztwhomNh8xkR9lJ" \
         --header 'Authorization: Bearer $TOKEN'

Observe that many fields expecting integer return float. The response that I got

{"tracks":[{"album":{"album_type":"album","artists":[{"external_urls":{"spotify":"https://open.spotify.com/artist/4AK6F7OLvEQ5QYCBNiQWHq"},"href":"https://api.spotify.com/v1/artists/4AK6F7OLvEQ5QYCBNiQWHq","id":"4AK6F7OLvEQ5QYCBNiQWHq","name":"One Direction","type":"artist","uri":"spotify:artist:4AK6F7OLvEQ5QYCBNiQWHq"}],"available_markets":["AR","AU","AT","BE","BO","BR","BG","CA","CL","CO","CR","CY","CZ","DK","DO","DE","EC","EE","SV","FI","FR","GR","GT","HN","HK","HU","IS","IE","IT","LV","LT","LU","MY","MT","MX","NL","NZ","NI","NO","PA","PY","PE","PH","PL","PT","SG","SK","ES","SE","CH","TW","TR","UY","US","GB","AD","LI","MC","ID","JP","TH","VN","RO","IL","ZA","SA","AE","BH","QA","OM","KW","EG","MA","DZ","TN","LB","JO","PS","IN","BY","KZ","MD","UA","AL","BA","HR","ME","MK","RS","SI","KR","BD","PK","LK","GH","KE","NG","TZ","UG","AG","AM","BS","BB","BZ","BT","BW","BF","CV","CW","DM","FJ","GM","GE","GD","GW","GY","HT","JM","KI","LS","LR","MW","MV","ML","MH","FM","NA","NR","NE","PW","PG","WS","SM","ST","SN","SC","SL","SB","KN","LC","VC","SR","TL","TO","TT","TV","VU","AZ","BN","BI","KH","CM","TD","KM","GQ","SZ","GA","GN","KG","LA","MO","MR","MN","NP","RW","TG","UZ","ZW","BJ","MG","MU","MZ","AO","CI","DJ","ZM","CD","CG","IQ","LY","TJ","VE","ET","XK"],"external_urls":{"spotify":"https://open.spotify.com/album/4gCNyS7pidfK3rKWhB3JOY"},"href":"https://api.spotify.com/v1/albums/4gCNyS7pidfK3rKWhB3JOY","id":"4gCNyS7pidfK3rKWhB3JOY","images":[{"url":"https://i.scdn.co/image/ab67616d0000b273d304ba2d71de306812eebaf4","width":640.0,"height":640.0},{"url":"https://i.scdn.co/image/ab67616d00001e02d304ba2d71de306812eebaf4","width":300.0,"height":300.0},{"url":"https://i.scdn.co/image/ab67616d00004851d304ba2d71de306812eebaf4","width":64.0,"height":64.0}],"is_playable":true,"name":"FOUR (Deluxe)","release_date":"2014-11-17","release_date_precision":"day","total_tracks":16.0,"type":"album","uri":"spotify:album:4gCNyS7pidfK3rKWhB3JOY"},"artists":[{"external_urls":{"spotify":"https://open.spotify.com/artist/4AK6F7OLvEQ5QYCBNiQWHq"},"href":"https://api.spotify.com/v1/artists/4AK6F7OLvEQ5QYCBNiQWHq","id":"4AK6F7OLvEQ5QYCBNiQWHq","name":"One Direction","type":"artist","uri":"spotify:artist:4AK6F7OLvEQ5QYCBNiQWHq"}],"available_markets":["AR","AU","AT","BE","BO","BR","BG","CA","CL","CO","CR","CY","CZ","DK","DO","DE","EC","EE","SV","FI","FR","GR","GT","HN","HK","HU","IS","IE","IT","LV","LT","LU","MY","MT","MX","NL","NZ","NI","NO","PA","PY","PE","PH","PL","PT","SG","SK","ES","SE","CH","TW","TR","UY","US","GB","AD","LI","MC","ID","JP","TH","VN","RO","IL","ZA","SA","AE","BH","QA","OM","KW","EG","MA","DZ","TN","LB","JO","PS","IN","BY","KZ","MD","UA","AL","BA","HR","ME","MK","RS","SI","KR","BD","PK","LK","GH","KE","NG","TZ","UG","AG","AM","BS","BB","BZ","BT","BW","BF","CV","CW","DM","FJ","GM","GE","GD","GW","GY","HT","JM","KI","LS","LR","MW","MV","ML","MH","FM","NA","NR","NE","PW","PG","WS","SM","ST","SN","SC","SL","SB","KN","LC","VC","SR","TL","TO","TT","TV","VU","AZ","BN","BI","KH","CM","TD","KM","GQ","SZ","GA","GN","KG","LA","MO","MR","MN","NP","RW","TG","UZ","ZW","BJ","MG","MU","MZ","AO","CI","DJ","ZM","CD","CG","IQ","LY","TJ","VE","ET","XK"],"disc_number":1.0,"duration_ms":226600.0,"explicit":false,"external_ids":{"isrc":"GBHMU1400165"},"external_urls":{"spotify":"https://open.spotify.com/track/5O2P9iiztwhomNh8xkR9lJ"},"href":"https://api.spotify.com/v1/tracks/5O2P9iiztwhomNh8xkR9lJ","id":"5O2P9iiztwhomNh8xkR9lJ","is_local":false,"is_playable":true,"name":"Night Changes","popularity":89.0,"preview_url":"https://p.scdn.co/mp3-preview/359be833b46b250c696bbb64caa5dc91f2a38c6a?cid=b28a574d8ad44fc7b5a89994431a8f88","track_number":7.0,"type":"track","uri":"spotify:track:5O2P9iiztwhomNh8xkR9lJ"}]}

Not sure if the above issue is only reproducible on my end because the same request on https://developer.spotify.com/documentation/web-api/reference/get-several-tracks still returns the correct type.

Found this issue when trying to investigate https://github.com/aome510/spotify-player/issues/383

<!-- gh-comment-id:1974932710 --> @aome510 commented on GitHub (Mar 2, 2024): I'm now getting the same error but with `get-several-tracks` API call. To reproduce, run ``` curl --request GET \ --url "https://api.spotify.com/v1/tracks?ids=5O2P9iiztwhomNh8xkR9lJ" \ --header 'Authorization: Bearer $TOKEN' ``` Observe that many fields expecting integer return float. The response that I got ``` {"tracks":[{"album":{"album_type":"album","artists":[{"external_urls":{"spotify":"https://open.spotify.com/artist/4AK6F7OLvEQ5QYCBNiQWHq"},"href":"https://api.spotify.com/v1/artists/4AK6F7OLvEQ5QYCBNiQWHq","id":"4AK6F7OLvEQ5QYCBNiQWHq","name":"One Direction","type":"artist","uri":"spotify:artist:4AK6F7OLvEQ5QYCBNiQWHq"}],"available_markets":["AR","AU","AT","BE","BO","BR","BG","CA","CL","CO","CR","CY","CZ","DK","DO","DE","EC","EE","SV","FI","FR","GR","GT","HN","HK","HU","IS","IE","IT","LV","LT","LU","MY","MT","MX","NL","NZ","NI","NO","PA","PY","PE","PH","PL","PT","SG","SK","ES","SE","CH","TW","TR","UY","US","GB","AD","LI","MC","ID","JP","TH","VN","RO","IL","ZA","SA","AE","BH","QA","OM","KW","EG","MA","DZ","TN","LB","JO","PS","IN","BY","KZ","MD","UA","AL","BA","HR","ME","MK","RS","SI","KR","BD","PK","LK","GH","KE","NG","TZ","UG","AG","AM","BS","BB","BZ","BT","BW","BF","CV","CW","DM","FJ","GM","GE","GD","GW","GY","HT","JM","KI","LS","LR","MW","MV","ML","MH","FM","NA","NR","NE","PW","PG","WS","SM","ST","SN","SC","SL","SB","KN","LC","VC","SR","TL","TO","TT","TV","VU","AZ","BN","BI","KH","CM","TD","KM","GQ","SZ","GA","GN","KG","LA","MO","MR","MN","NP","RW","TG","UZ","ZW","BJ","MG","MU","MZ","AO","CI","DJ","ZM","CD","CG","IQ","LY","TJ","VE","ET","XK"],"external_urls":{"spotify":"https://open.spotify.com/album/4gCNyS7pidfK3rKWhB3JOY"},"href":"https://api.spotify.com/v1/albums/4gCNyS7pidfK3rKWhB3JOY","id":"4gCNyS7pidfK3rKWhB3JOY","images":[{"url":"https://i.scdn.co/image/ab67616d0000b273d304ba2d71de306812eebaf4","width":640.0,"height":640.0},{"url":"https://i.scdn.co/image/ab67616d00001e02d304ba2d71de306812eebaf4","width":300.0,"height":300.0},{"url":"https://i.scdn.co/image/ab67616d00004851d304ba2d71de306812eebaf4","width":64.0,"height":64.0}],"is_playable":true,"name":"FOUR (Deluxe)","release_date":"2014-11-17","release_date_precision":"day","total_tracks":16.0,"type":"album","uri":"spotify:album:4gCNyS7pidfK3rKWhB3JOY"},"artists":[{"external_urls":{"spotify":"https://open.spotify.com/artist/4AK6F7OLvEQ5QYCBNiQWHq"},"href":"https://api.spotify.com/v1/artists/4AK6F7OLvEQ5QYCBNiQWHq","id":"4AK6F7OLvEQ5QYCBNiQWHq","name":"One Direction","type":"artist","uri":"spotify:artist:4AK6F7OLvEQ5QYCBNiQWHq"}],"available_markets":["AR","AU","AT","BE","BO","BR","BG","CA","CL","CO","CR","CY","CZ","DK","DO","DE","EC","EE","SV","FI","FR","GR","GT","HN","HK","HU","IS","IE","IT","LV","LT","LU","MY","MT","MX","NL","NZ","NI","NO","PA","PY","PE","PH","PL","PT","SG","SK","ES","SE","CH","TW","TR","UY","US","GB","AD","LI","MC","ID","JP","TH","VN","RO","IL","ZA","SA","AE","BH","QA","OM","KW","EG","MA","DZ","TN","LB","JO","PS","IN","BY","KZ","MD","UA","AL","BA","HR","ME","MK","RS","SI","KR","BD","PK","LK","GH","KE","NG","TZ","UG","AG","AM","BS","BB","BZ","BT","BW","BF","CV","CW","DM","FJ","GM","GE","GD","GW","GY","HT","JM","KI","LS","LR","MW","MV","ML","MH","FM","NA","NR","NE","PW","PG","WS","SM","ST","SN","SC","SL","SB","KN","LC","VC","SR","TL","TO","TT","TV","VU","AZ","BN","BI","KH","CM","TD","KM","GQ","SZ","GA","GN","KG","LA","MO","MR","MN","NP","RW","TG","UZ","ZW","BJ","MG","MU","MZ","AO","CI","DJ","ZM","CD","CG","IQ","LY","TJ","VE","ET","XK"],"disc_number":1.0,"duration_ms":226600.0,"explicit":false,"external_ids":{"isrc":"GBHMU1400165"},"external_urls":{"spotify":"https://open.spotify.com/track/5O2P9iiztwhomNh8xkR9lJ"},"href":"https://api.spotify.com/v1/tracks/5O2P9iiztwhomNh8xkR9lJ","id":"5O2P9iiztwhomNh8xkR9lJ","is_local":false,"is_playable":true,"name":"Night Changes","popularity":89.0,"preview_url":"https://p.scdn.co/mp3-preview/359be833b46b250c696bbb64caa5dc91f2a38c6a?cid=b28a574d8ad44fc7b5a89994431a8f88","track_number":7.0,"type":"track","uri":"spotify:track:5O2P9iiztwhomNh8xkR9lJ"}]} ``` Not sure if the above issue is only reproducible on my end because the same request on https://developer.spotify.com/documentation/web-api/reference/get-several-tracks still returns the correct type. Found this issue when trying to investigate https://github.com/aome510/spotify-player/issues/383
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

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

I have to say, it's "scope creep" of Spotify's bug, other developers have reported the same observation in other endpoints, it becomes less possible to be patched and bypassed individually by the community-driven library, this problem has to be fixed by the Spotify itself.

<!-- gh-comment-id:1974941039 --> @ramsayleung commented on GitHub (Mar 2, 2024): I have to say, it's "scope creep" of Spotify's bug, other developers have reported the same observation in [other endpoints](https://community.spotify.com/t5/Spotify-for-Developers/The-response-type-of-artist-endpoint-is-marked-as-Integer-in/m-p/5911749/highlight/true#M12875), it becomes less possible to be patched and bypassed individually by the community-driven library, this problem has to be fixed by the Spotify itself.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

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

I have to say, it's "scope creep" of Spotify's bug, other developers have reported the same observation in other endpoints, it becomes less possible to be patched and bypassed individually by the community-driven library, this problem has to be fixed by the Spotify itself.

Yeah, I agree. At the same time, it's kinda frustrating to see that Spotify doesn't seem to take any actions.

<!-- gh-comment-id:1974942578 --> @aome510 commented on GitHub (Mar 2, 2024): > I have to say, it's "scope creep" of Spotify's bug, other developers have reported the same observation in [other endpoints](https://community.spotify.com/t5/Spotify-for-Developers/The-response-type-of-artist-endpoint-is-marked-as-Integer-in/m-p/5911749/highlight/true#M12875), it becomes less possible to be patched and bypassed individually by the community-driven library, this problem has to be fixed by the Spotify itself. Yeah, I agree. At the same time, it's kinda frustrating to see that Spotify doesn't seem to take any actions.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Mar 3, 2024):

The new version of RSpotify would like to pend for a while for the response from Spotify, since it's meanless to release a new version while Spotify keeps breaking their endpoints, the community is unable to catch up to release new patch.

<!-- gh-comment-id:1975012849 --> @ramsayleung commented on GitHub (Mar 3, 2024): The new version of RSpotify would like to pend for a while for the response from Spotify, since it's meanless to release a new version while Spotify keeps breaking their endpoints, the community is unable to catch up to release new patch.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ed9w2in6 commented on GitHub (Mar 7, 2024):

@aome510 @ramsayleung
Seems to be fixed ^_^

As expected this is caused by some library that they are using.

I am using spotify_player today and found that at the the artist endpoint works now.

<!-- gh-comment-id:1982655921 --> @ed9w2in6 commented on GitHub (Mar 7, 2024): @aome510 @ramsayleung [Seems to be fixed](https://community.spotify.com/t5/Spotify-for-Developers/duration-ms-suddenly-returning-float-instead-of-int/m-p/5911447#M12863) ^_^ As expected this is caused by some library that they are using. I am using `spotify_player` today and found that at the the `artist` endpoint works now.
kerem commented 2026-02-27 20:23:25 +03:00
Author
Owner
Copy link

@ramsayleung commented on GitHub (Mar 8, 2024):

Closing since this issue has been resolved by Spotify.

<!-- gh-comment-id:1986263329 --> @ramsayleung commented on GitHub (Mar 8, 2024): Closing since this issue has been resolved by Spotify.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
ramsay/upgrade-0.16.1
dependabot/cargo/sha2-0.11.0
ramsay/upgrade-to-v0.16
ramsay/deprecate-removed-renamed-field
ramsay/migrate-to-new-endpoint
ramsay/deprecate-removed-endpoints
dependabot/cargo/strum-0.28.0
dependabot/cargo/reqwest-middleware-0.5.1
dependabot/cargo/reqwest-0.13.1
ramsay/upgrade-to-0.15.3
ramsay/upgrade-to-0.15.2
dependabot/cargo/ureq-3.1.2
ramsay/upgrade-dependencies
ramsay/upgrade-to-0.15.1
ramsay/fix-malformed-json
ramsay/upgrade-to-v0.15.0
ramsay/allow-enum-unknown-variant
ramsay/upgrade-to-0.14
ramsay/add_tcplistern_for_callback
ramsay/fix-clippy-error
ramsay/update-doc
ramsay/fix-endless-sequence
ramsay/publish-crate-workflow-test
ramsay/fix-pkce-refresh-token
ramsay/pkce_auth_refresh_token
ramsay_add_test_for_collectionyourepisodes
better-webapp
ramsay_fix_token_expired
percent-search
refresh_token_rwlock
ramsay_convert_result_inside_endpoint
streaming
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.0
v0.13.3
v0.13.2
v0.13.1
v0.13.0
v0.12.0
v0.11.7
v0.11.6
v0.10.0
v0.11.5
v0.11.5.0
v0.11.4
v0.11.3
v0.11.2
v0.11.1
v0.11.0
v0.11.5.1
v0.9
v0.9-alpha
Labels
Clear labels   
Stale

   
bug

   
discussion

   
enhancement

   
good first issue

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/rspotify#150
No description provided.