starred/spotify-player
1
0
Fork 0
mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 09:25:49 +03:00
Code Issues 242 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #890] Failed to handle client request: status code 429 Too Many Requests #535

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

Originally created by @DavidHospital on GitHub (Dec 22, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/890

Describe the bug
spotify-player seemingly cannot make any requests to Spotify it seems. Any action that requires a request to spotify fails silently and the TUI is stuck loading forever.

To Reproduce
I am not sure to be honest, this just started happening every time I try to use spotify-player starting today. I have double checked there aren't any extra instancing of it running in the background.

Expected behaviour
I expect the basic functions of the app to work.

Log and backtrace
An example of some of the logs:

2025-12-22T18:26:42.112431Z  INFO client_request{request=GetContext(Album(AlbumId("6DxidEI7EhF8md8ev83iNY")))}: spotify_player::client: Get album context: spotify:album:6DxidEI7EhF8md8ev83iNY
2025-12-22T18:26:42.176631Z ERROR client_request{request=GetContext(Album(AlbumId("6DxidEI7EhF8md8ev83iNY")))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests

It is the same 429 error for any action.

Environment

  • OS: Ubuntu 22.04.5 LTS x86_64
  • Application version: 0.21.2
  • Application features: default features (ie. cargo install spotify_player)

Additional context
This began happening this morning (around 10am EST) when I loaded it up to play some music. I've tried it again periodically throughout the day with no luck. I've also double checked my other devices to see if, for example, I could use Spotify on my phone; no issues there which rules out a problem with my account, etc.

Originally created by @DavidHospital on GitHub (Dec 22, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/890 **Describe the bug** `spotify-player` seemingly cannot make any requests to Spotify it seems. Any action that requires a request to spotify fails silently and the TUI is stuck loading forever. **To Reproduce** I am not sure to be honest, this just started happening every time I try to use `spotify-player` starting today. I have double checked there aren't any extra instancing of it running in the background. **Expected behaviour** I expect the basic functions of the app to work. **Log and backtrace** An example of some of the logs: ``` 2025-12-22T18:26:42.112431Z INFO client_request{request=GetContext(Album(AlbumId("6DxidEI7EhF8md8ev83iNY")))}: spotify_player::client: Get album context: spotify:album:6DxidEI7EhF8md8ev83iNY 2025-12-22T18:26:42.176631Z ERROR client_request{request=GetContext(Album(AlbumId("6DxidEI7EhF8md8ev83iNY")))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests ``` It is the same 429 error for any action. **Environment** - OS: Ubuntu 22.04.5 LTS x86_64 - Application version: 0.21.2 - Application features: default features (ie. `cargo install spotify_player`) **Additional context** This began happening this morning (around 10am EST) when I loaded it up to play some music. I've tried it again periodically throughout the day with no luck. I've also double checked my other devices to see if, for example, I could use Spotify on my phone; no issues there which rules out a problem with my account, etc.
kerem 2026-03-02 23:48:24 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

I noticed the same thing when coming back to this project and start working on it again today (bad timings 😢 ).

The rate-limit issue happens when making API requests to the official Spotify client (client ID: 65b708073fc0480ea92a077233ca87bd). Hopefully, this is just a temporary thing

<!-- gh-comment-id:3683605188 --> @aome510 commented on GitHub (Dec 22, 2025): I noticed the same thing when coming back to this project and start working on it again today (bad timings 😢 ). The rate-limit issue happens when making API requests to the official Spotify client (client ID: `65b708073fc0480ea92a077233ca87bd`). Hopefully, this is just a temporary thing
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in https://github.com/aome510/spotify-player/pull/891.

With the above change, API requests will be sent to user-provided client instead of the official Spotify client. One limitation of this workaround is that with user-provided client, spotify_player will have a limited API access compared to the full access when using the official Spotify client (see https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api for more details)

Just a note that you will need to set a client_id in app.toml to enable the user-provided client (see this doc for more details)

<!-- gh-comment-id:3683727470 --> @aome510 commented on GitHub (Dec 22, 2025): In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in https://github.com/aome510/spotify-player/pull/891. With the above change, API requests will be sent to **user-provided client instead of the official Spotify client**. One limitation of this workaround is that with user-provided client, `spotify_player` will have a limited API access compared to the full access when using the official Spotify client (see https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api for more details) Just a note that you will need to set a `client_id` in `app.toml` to enable the user-provided client (see [this doc](https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect) for more details)
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@DavidHospital commented on GitHub (Dec 22, 2025):

In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in #891.

Thanks for the quick response! This branch worked for navigating around the TUI, like selecting an album, etc. but now I'm getting some 401s when trying to play anything:

2025-12-22T19:20:55.323569Z ERROR client_request{request=Player(TransferPlayback("a12000aa-ac08-45c5-85fa-1f6b79f52c9f", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized
2025-12-22T19:20:56.557990Z ERROR client_request{request=Player(StartPlayback(Context(Album(AlbumId("6FRN2BwvClQEMsG2I4Cofb")), Some(Uri("spotify:track:6677v7VjQsuA6BRFQxQcmG"))), None))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized

I have client_id set (had this set as long as I've been using spotify-player). Tried to switch device to spotify-player as well, which did nothing.

Could this be a user error?

<!-- gh-comment-id:3683821740 --> @DavidHospital commented on GitHub (Dec 22, 2025): > In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in [#891](https://github.com/aome510/spotify-player/pull/891). Thanks for the quick response! This branch worked for navigating around the TUI, like selecting an album, etc. but now I'm getting some 401s when trying to play anything: ``` 2025-12-22T19:20:55.323569Z ERROR client_request{request=Player(TransferPlayback("a12000aa-ac08-45c5-85fa-1f6b79f52c9f", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized 2025-12-22T19:20:56.557990Z ERROR client_request{request=Player(StartPlayback(Context(Album(AlbumId("6FRN2BwvClQEMsG2I4Cofb")), Some(Uri("spotify:track:6677v7VjQsuA6BRFQxQcmG"))), None))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized ``` I have `client_id` set (had this set as long as I've been using `spotify-player`). Tried to switch device to `spotify-player` as well, which did nothing. Could this be a user error?
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in #891.

Thanks for the quick response! This branch worked for navigating around the TUI, like selecting an album, etc. but now I'm getting some 401s when trying to play anything:

2025-12-22T19:20:55.323569Z ERROR client_request{request=Player(TransferPlayback("a12000aa-ac08-45c5-85fa-1f6b79f52c9f", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized
2025-12-22T19:20:56.557990Z ERROR client_request{request=Player(StartPlayback(Context(Album(AlbumId("6FRN2BwvClQEMsG2I4Cofb")), Some(Uri("spotify:track:6677v7VjQsuA6BRFQxQcmG"))), None))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized

I have client_id set (had this set as long as I've been using spotify-player). Tried to switch device to spotify-player as well, which did nothing.

Could this be a user error?

hmmm, playing or transferring playback works well for me. Can you try rm ~/.cache/spotify-player/user_client_token.json and re-run the app?

<!-- gh-comment-id:3683842742 --> @aome510 commented on GitHub (Dec 22, 2025): > > In case anyone wants a temporary workaround, I got this app working using user-provided client instead of the integrated client to make API calls in [#891](https://github.com/aome510/spotify-player/pull/891). > > Thanks for the quick response! This branch worked for navigating around the TUI, like selecting an album, etc. but now I'm getting some 401s when trying to play anything: > > ``` > 2025-12-22T19:20:55.323569Z ERROR client_request{request=Player(TransferPlayback("a12000aa-ac08-45c5-85fa-1f6b79f52c9f", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized > 2025-12-22T19:20:56.557990Z ERROR client_request{request=Player(StartPlayback(Context(Album(AlbumId("6FRN2BwvClQEMsG2I4Cofb")), Some(Uri("spotify:track:6677v7VjQsuA6BRFQxQcmG"))), None))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 401 Unauthorized > ``` > > I have `client_id` set (had this set as long as I've been using `spotify-player`). Tried to switch device to `spotify-player` as well, which did nothing. > > Could this be a user error? hmmm, playing or transferring playback works well for me. Can you try `rm ~/.cache/spotify-player/user_client_token.json` and re-run the app?
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@DavidHospital commented on GitHub (Dec 22, 2025):

hmmm, playing or transferring playback works well for me. Can you try rm ~/.cache/spotify-player/user_client_token.json and re-run the app?

Hmm tried that, regenerated the token. Still not working - same 401 error in the logs

<!-- gh-comment-id:3683851441 --> @DavidHospital commented on GitHub (Dec 22, 2025): > hmmm, playing or transferring playback works well for me. Can you try `rm ~/.cache/spotify-player/user_client_token.json` and re-run the app? Hmm tried that, regenerated the token. Still not working - same 401 error in the logs
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

Can you try rm ~/.cache/spotify-player/credentials.json and re-run as well?

<!-- gh-comment-id:3683861911 --> @aome510 commented on GitHub (Dec 22, 2025): Can you try `rm ~/.cache/spotify-player/credentials.json` and re-run as well?
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@DavidHospital commented on GitHub (Dec 22, 2025):

Can you try rm ~/.cache/spotify-player/credentials.json and re-run as well?

Same thing :(

<!-- gh-comment-id:3683869980 --> @DavidHospital commented on GitHub (Dec 22, 2025): > Can you try `rm ~/.cache/spotify-player/credentials.json` and re-run as well? Same thing :(
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

@DavidHospital I can reproduce by creating a new Spotify app myself, so i guess the 401 thing is an issue with newer app. Lemme try to figure out how to fix this and if it's possible. FWIW, this is still a workaround

<!-- gh-comment-id:3683906097 --> @aome510 commented on GitHub (Dec 22, 2025): @DavidHospital I can reproduce by creating a new Spotify app myself, so i guess the 401 thing is an issue with newer app. Lemme try to figure out how to fix this and if it's possible. FWIW, this is still a workaround
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

@DavidHospital updated in https://github.com/aome510/spotify-player/pull/891/commits/c2d4a92860499db689b44fdd29aead966f05e78b. Can you try rm ~/.cache/spotify-player/user_client_token.json and rerun the app with the new change?

<!-- gh-comment-id:3683931838 --> @aome510 commented on GitHub (Dec 22, 2025): @DavidHospital updated in https://github.com/aome510/spotify-player/pull/891/commits/c2d4a92860499db689b44fdd29aead966f05e78b. Can you try `rm ~/.cache/spotify-player/user_client_token.json` and rerun the app with the new change?
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@DavidHospital commented on GitHub (Dec 22, 2025):

that did it! thank you. I will continue using this branch for now then

<!-- gh-comment-id:3683945952 --> @DavidHospital commented on GitHub (Dec 22, 2025): that did it! thank you. I will continue using this branch for now then
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 22, 2025):

I plan to merge the PR soon to unblock working on other things and will revert the workaround once the official Spotify client is back to normal

<!-- gh-comment-id:3683950632 --> @aome510 commented on GitHub (Dec 22, 2025): I plan to merge the PR soon to unblock working on other things and will revert the workaround once the official Spotify client is back to normal
kerem commented 2026-03-02 23:48:26 +03:00
Author
Owner
Copy link

@feskslo commented on GitHub (Dec 23, 2025):

Rebuilt with the linked commit c2d4a92, and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely.

Environment: Pop!_OS 24.04.
Features image,notify,media-control,fzf
Rev c2d4a92860

Errors seen in log:
67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)
68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)

Edit: Installed again without feature "image" and it seems to work fine now

<!-- gh-comment-id:3685900537 --> @feskslo commented on GitHub (Dec 23, 2025): Rebuilt with the linked commit c2d4a92, and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely. Environment: Pop!_OS 24.04. Features image,notify,media-control,fzf Rev c2d4a92860499db689b44fdd29aead966f05e78b Errors seen in log: 67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) 68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) Edit: Installed again without feature "image" and it seems to work fine now
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 23, 2025):

Related: https://github.com/hrkfdn/ncspot/issues/1757#issuecomment-3685875360. ncspot users also encountered the same issue. It seems spotify implements much stricter rate limit policy resulting in the above error. I wonder if this change is something permanent 🤔

<!-- gh-comment-id:3686919971 --> @aome510 commented on GitHub (Dec 23, 2025): Related: https://github.com/hrkfdn/ncspot/issues/1757#issuecomment-3685875360. `ncspot` users also encountered the same issue. It seems spotify implements much stricter rate limit policy resulting in the above error. I wonder if this change is something permanent 🤔
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@alaughlin commented on GitHub (Dec 23, 2025):

Rebuilt with the linked commit c2d4a92, and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely.

Environment: Pop!_OS 24.04. Features image,notify,media-control,fzf Rev c2d4a92

Errors seen in log: 67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) 68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)

Edit: Installed again without feature "image" and it seems to work fine now

Also having this problem. Would rather not build without the image feature so will wait to see what's up.

<!-- gh-comment-id:3687936099 --> @alaughlin commented on GitHub (Dec 23, 2025): > Rebuilt with the linked commit [c2d4a92](https://github.com/aome510/spotify-player/commit/c2d4a92860499db689b44fdd29aead966f05e78b), and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely. > > Environment: Pop!_OS 24.04. Features image,notify,media-control,fzf Rev [c2d4a92](https://github.com/aome510/spotify-player/commit/c2d4a92860499db689b44fdd29aead966f05e78b) > > Errors seen in log: 67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) 68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) > > Edit: Installed again without feature "image" and it seems to work fine now Also having this problem. Would rather not build without the image feature so will wait to see what's up.
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@B1T3X commented on GitHub (Dec 24, 2025):

Rebuilt with the linked commit c2d4a92, and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely.

Environment: Pop!_OS 24.04. Features image,notify,media-control,fzf Rev c2d4a92

Errors seen in log: 67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) 68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)

Edit: Installed again without feature "image" and it seems to work fine now

Exact same problem, exact same solution
On a MacOS Sequioa 15.7.1 (24G231)

<!-- gh-comment-id:3689456787 --> @B1T3X commented on GitHub (Dec 24, 2025): > Rebuilt with the linked commit [c2d4a92](https://github.com/aome510/spotify-player/commit/c2d4a92860499db689b44fdd29aead966f05e78b), and playback now works, no more error 429. Unfortunately, now the spotify_player UI becomes unresponsive as soon as playback begins. Librespot_playback is doing its thing in the background and playing music just fine, but the UI freezes as soon as playback starts. Stays frozen/unresponsive indefinitely. > > Environment: Pop!_OS 24.04. Features image,notify,media-control,fzf Rev [c2d4a92](https://github.com/aome510/spotify-player/commit/c2d4a92860499db689b44fdd29aead966f05e78b) > > Errors seen in log: 67 │ 2025-12-23T09:19:17.556322Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) 68 │ 2025-12-23T09:19:28.559292Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode) > > Edit: Installed again without feature "image" and it seems to work fine now Exact same problem, exact same solution On a MacOS Sequioa 15.7.1 (24G231)
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 24, 2025):

I'm using MacOS 26.1 and running the app with cargo run --features image,notify,media-control,fzf works fine for me without any issue on the latest commit of master

<!-- gh-comment-id:3689906852 --> @aome510 commented on GitHub (Dec 24, 2025): I'm using MacOS 26.1 and running the app with `cargo run --features image,notify,media-control,fzf` works fine for me without any issue on the latest commit of `master`
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@TogiFerretFerret commented on GitHub (Dec 24, 2025):

I see freezing, but interestingly when I remove the image flag (kitty image protocol in ghostty for me) the freezing doesn't occur as well.
Is the image causing some hanging due to the request for the album art or something? or is it like the control codes?

<!-- gh-comment-id:3690036376 --> @TogiFerretFerret commented on GitHub (Dec 24, 2025): I see freezing, but interestingly when I remove the image flag (kitty image protocol in ghostty for me) the freezing doesn't occur as well. Is the image causing some hanging due to the request for the album art or something? or is it like the control codes?
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 24, 2025):

hmm maybe related to recent viuer upgrade to 0.11.0 in github.com/aome510/spotify-player@506c3318e6/spotify_player/Cargo.toml (L45G). Can you try to downgrade it to 0.9.2 to see if it fixes the issue?

<!-- gh-comment-id:3690084028 --> @aome510 commented on GitHub (Dec 24, 2025): hmm maybe related to recent viuer upgrade to `0.11.0` in https://github.com/aome510/spotify-player/blob/506c3318e6b1d02d35aa0bfdef19e5f07df5812d/spotify_player/Cargo.toml#L45G. Can you try to downgrade it to `0.9.2` to see if it fixes the issue?
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@Flynatol commented on GitHub (Dec 24, 2025):

I was just testing this and yes downgrading viuer fixes the issue.

<!-- gh-comment-id:3690091814 --> @Flynatol commented on GitHub (Dec 24, 2025): I was just testing this and yes downgrading viuer fixes the issue.
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@TogiFerretFerret commented on GitHub (Dec 24, 2025):

I also wrote a PR that doesn't need to downgrade viuer. #897

<!-- gh-comment-id:3690102110 --> @TogiFerretFerret commented on GitHub (Dec 24, 2025): I also wrote a PR that doesn't need to downgrade viuer. #897
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@pstumpf commented on GitHub (Dec 25, 2025):

Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log.

<!-- gh-comment-id:3691135483 --> @pstumpf commented on GitHub (Dec 25, 2025): Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log.
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@Alexander3a commented on GitHub (Dec 25, 2025):

Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log.

yeah ever since the patch it has been broken but i seems to be a change on spotify`s end if u ask me

<!-- gh-comment-id:3691590829 --> @Alexander3a commented on GitHub (Dec 25, 2025): > Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log. yeah ever since the patch it has been broken but i seems to be a change on spotify`s end if u ask me
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Dec 28, 2025):

I also wrote a PR that doesn't need to downgrade viuer. #897

Thanks @TogiFerretFerret for the patch. It's not clear to me why this issue happened (I couldn't reproduce with kitty 0.44.0 on MacOS) and if the above patch is enough

<!-- gh-comment-id:3695129850 --> @aome510 commented on GitHub (Dec 28, 2025): > I also wrote a PR that doesn't need to downgrade viuer. [#897](https://github.com/aome510/spotify-player/pull/897) Thanks @TogiFerretFerret for the patch. It's not clear to me why this issue happened (I couldn't reproduce with kitty `0.44.0` on MacOS) and if the above patch is enough
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@YourRobotOverlord commented on GitHub (Dec 29, 2025):

Darn, from the Spotify dashboard: "New integrations are currently on hold..." so we can't use the user-provided client workaround either now. 😒

<!-- gh-comment-id:3695162256 --> @YourRobotOverlord commented on GitHub (Dec 29, 2025): Darn, from the Spotify dashboard: "New integrations are currently on hold..." so we can't use the user-provided client workaround either now. 😒
kerem commented 2026-03-02 23:48:27 +03:00
Author
Owner
Copy link

@ypurpl commented on GitHub (Dec 29, 2025):

yeah ever since the patch it has been broken but i seems to be a change on spotify`s end if u ask me

guess we gotta wait. hopefully it goes back to before this issue was created

<!-- gh-comment-id:3695199394 --> @ypurpl commented on GitHub (Dec 29, 2025): > yeah ever since the patch it has been broken but i seems to be a change on spotify`s end if u ask me guess we gotta wait. hopefully it goes back to before this issue was created
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@pstumpf commented on GitHub (Dec 29, 2025):

Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log.

For the record, this is now successfully worked around by github.com/aome510/spotify-player@baae5110a9

<!-- gh-comment-id:3696331614 --> @pstumpf commented on GitHub (Dec 29, 2025): > Using the latest HEAD, playback from saved playlists and albums works fine, but attempting to open an artist’s page still results in endless "Loading ..." with a 429 error in the log. For the record, this is now successfully worked around by https://github.com/aome510/spotify-player/commit/baae5110a91b3d4a32bbcc7e0026c77d9d0ff942
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@ruinedraziel commented on GitHub (Dec 29, 2025):

So is this issue still happening?
baae511 didn't fix on my end, same behavior, do I need to disable some feature?

<!-- gh-comment-id:3697279277 --> @ruinedraziel commented on GitHub (Dec 29, 2025): So is this issue still happening? baae511 didn't fix on my end, same behavior, do I need to disable some feature?
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@ypurpl commented on GitHub (Dec 30, 2025):

So is this issue still happening? baae511 didn't fix on my end, same behavior, do I need to disable some feature?

Disable any image-related features if necessary, but there are some server-sided issues that we can only wait for

<!-- gh-comment-id:3700685583 --> @ypurpl commented on GitHub (Dec 30, 2025): > So is this issue still happening? [baae511](https://github.com/aome510/spotify-player/commit/baae5110a91b3d4a32bbcc7e0026c77d9d0ff942) didn't fix on my end, same behavior, do I need to disable some feature? Disable any image-related features if necessary, but there are some server-sided issues that we can only wait for
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@williamwu062 commented on GitHub (Jan 6, 2026):

are the latest workarounds in homebrew? Was having trouble with 429 issue there.

<!-- gh-comment-id:3716622094 --> @williamwu062 commented on GitHub (Jan 6, 2026): are the latest workarounds in homebrew? Was having trouble with 429 issue there.
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@pstumpf commented on GitHub (Jan 7, 2026):

I do not think this will be resolved on Spotify's end soon, so maybe it’s best to just do a release with the current changes?

<!-- gh-comment-id:3720832207 --> @pstumpf commented on GitHub (Jan 7, 2026): I do not think this will be resolved on Spotify's end soon, so maybe it’s best to just do a release with the current changes?
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Jan 7, 2026):

Yep I can release a patched version later this week if Spotify doesn’t resolve the issue by then

<!-- gh-comment-id:3721094259 --> @aome510 commented on GitHub (Jan 7, 2026): Yep I can release a patched version later this week if Spotify doesn’t resolve the issue by then
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@Sbagchee commented on GitHub (Jan 8, 2026):

Yep I can release a patched version later this week if Spotify doesn’t resolve the issue by then

You rock!

<!-- gh-comment-id:3721326065 --> @Sbagchee commented on GitHub (Jan 8, 2026): > Yep I can release a patched version later this week if Spotify doesn’t resolve the issue by then You rock!
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@kohane27 commented on GitHub (Jan 8, 2026):

@pstumpf Apologies for pinging. But what current workaround is working?
I tried building on current master branch which has github.com/aome510/spotify-player@baae5110a9
It builds and the TUI opened, but I got the following error:

No playback found. Please start a new playback.
Make sure there is a running Spotify device and try to connect to one using the `SwitchDevice` command.
You may also need to set up Spotify Connect to see available devices as in https://github.com/aome510/spotify-player#spotify-connect.

I never enabled Spotify connect but now it's current not available with "New integrations are currently on hold while we make updates to improve reliability and performance." Even though re-authentication worked after rm ~/.cache/spotify-player/credentials.json.
Is it catch-22 that it won't work for me case then, i.e., current API rate-limiting changes and users without "Spotify connect" enabled? I have been not been able to use spotify-player for literally 2 weeks now. Any input is much appreciated. Thank you!

<!-- gh-comment-id:3721334757 --> @kohane27 commented on GitHub (Jan 8, 2026): @pstumpf Apologies for pinging. But what current workaround is working? I tried building on current `master` branch which has https://github.com/aome510/spotify-player/commit/baae5110a91b3d4a32bbcc7e0026c77d9d0ff942 It builds and the TUI opened, but I got the following error: ``` No playback found. Please start a new playback. Make sure there is a running Spotify device and try to connect to one using the `SwitchDevice` command. You may also need to set up Spotify Connect to see available devices as in https://github.com/aome510/spotify-player#spotify-connect. ``` I never enabled Spotify connect but now it's current not available with "New integrations are currently on hold while we make updates to improve reliability and performance." Even though re-authentication worked after `rm ~/.cache/spotify-player/credentials.json`. Is it catch-22 that it won't work for me case then, i.e., current API rate-limiting changes and users without "Spotify connect" enabled? I have been not been able to use spotify-player for literally 2 weeks now. Any input is much appreciated. Thank you!
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Jan 8, 2026):

@kohane27 please refer to https://github.com/aome510/spotify-player/issues/890#issuecomment-3683727470

You need to use user-provided client in order for the workaround on main to work. Spotify currently disallows creating new client as indicated by New integrations are currently on hold while we make updates to improve reliability and performance. As a workaround, you can try to specify my client's ID instead: b28a574d8ad44fc7b5a89994431a8f88

I will also update the code accordingly to use my client's ID as a fallback for folks who couldn't register a new Spotify app due to above restrictions before releasing a new version

<!-- gh-comment-id:3721389914 --> @aome510 commented on GitHub (Jan 8, 2026): @kohane27 please refer to https://github.com/aome510/spotify-player/issues/890#issuecomment-3683727470 You need to use user-provided client in order for the workaround on `main` to work. Spotify currently disallows creating new client as indicated by `New integrations are currently on hold while we make updates to improve reliability and performance`. As a workaround, you can try to specify my client's ID instead: `b28a574d8ad44fc7b5a89994431a8f88` I will also update the code accordingly to use my client's ID as a fallback for folks who couldn't register a new Spotify app due to above restrictions before releasing a new version
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Jan 8, 2026):

release a new version https://github.com/aome510/spotify-player/releases/tag/v0.21.3 which should workaround the rate-limit issue discussed here

<!-- gh-comment-id:3721472482 --> @aome510 commented on GitHub (Jan 8, 2026): release a new version https://github.com/aome510/spotify-player/releases/tag/v0.21.3 which should workaround the rate-limit issue discussed here
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@unexist commented on GitHub (Jan 16, 2026):

Thanks for the hard work - I know this is an annoying change on Spotify's side.

Just a minor request: There are many things that don't work properly at the moment (no offense), but would it be feasible to replace the "Loading..." text with an actual error message? I see this quite frequently and I am never sure if it run into the well-known 429 issue or something else is amiss.

<!-- gh-comment-id:3758518316 --> @unexist commented on GitHub (Jan 16, 2026): Thanks for the hard work - I know this is an annoying change on Spotify's side. Just a minor request: There are many things that don't work properly at the moment (no offense), but would it be feasible to replace the "Loading..." text with an actual error message? I see this quite frequently and I am never sure if it run into the well-known 429 issue or something else is amiss.
kerem commented 2026-03-02 23:48:28 +03:00
Author
Owner
Copy link

@ldreux commented on GitHub (Feb 6, 2026):

Hello, I tried with the official spotify client id but I have always status code 429 Too Many Requests with spotify_player 0.21.3. Have you another workaround to try ?

<!-- gh-comment-id:3858730385 --> @ldreux commented on GitHub (Feb 6, 2026): Hello, I tried with the official spotify client id but I have always status code 429 Too Many Requests with spotify_player 0.21.3. Have you another workaround to try ?
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 7, 2026):

look like folks from ncspot figured out how to resolve the issue in https://github.com/hrkfdn/ncspot/issues/1757#issuecomment-3792564030 by using a client ID predated spotify API changes. The one I'm using right now didn't register extended quota mode so the capability is limited (see https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api)

I'm going to integrate ncspot's client ID to spotify-player and hopefully it will bring back all previously supported functionality

<!-- gh-comment-id:3863898850 --> @aome510 commented on GitHub (Feb 7, 2026): look like folks from `ncspot` figured out how to resolve the issue in https://github.com/hrkfdn/ncspot/issues/1757#issuecomment-3792564030 by using a client ID predated spotify API changes. [The one I'm using right now](https://github.com/aome510/spotify-player/blob/9ccb5bf852420129adb3c57a05d202ab2bb2081d/spotify_player/src/config/mod.rs#L280) didn't register [extended quota mode](https://developer.spotify.com/documentation/web-api/concepts/quota-modes) so the capability is limited (see https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api) I'm going to integrate ncspot's client ID to `spotify-player` and hopefully it will bring back all previously supported functionality
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 7, 2026):

#918 is merged. I want to ask folks in this thread to test it to see if everything works fine after the integration.

Steps to test ncspot client ID integration.

  • checkout project latest commit
  • uncomment client_id in ~/.config/spotify-player/app.toml (to use fallback ncspot's client ID)
  • remove cached user client token: rm ~/.cache/spotify-player/user_client_token.json
  • build and run the app, i.e. with cargo run
  • check if everything works as intended: streaming, spotify connect with different devices, browsing spotify-generated playlists, seeing related artists, etc
<!-- gh-comment-id:3863974781 --> @aome510 commented on GitHub (Feb 7, 2026): #918 is merged. I want to ask folks in this thread to test it to see if everything works fine after the integration. Steps to test `ncspot` client ID integration. - checkout project [latest commit](https://github.com/aome510/spotify-player/commit/c3d39faa02dc7ec40d6a6352b838a261e896663b) - uncomment `client_id` in `~/.config/spotify-player/app.toml` (to use [fallback `ncspot`'s client ID](https://github.com/aome510/spotify-player/blob/c3d39faa02dc7ec40d6a6352b838a261e896663b/spotify_player/src/config/mod.rs#L277-L284)) - remove cached user client token: `rm ~/.cache/spotify-player/user_client_token.json` - build and run the app, i.e. with `cargo run` - check if everything works as intended: streaming, spotify connect with different devices, browsing spotify-generated playlists, seeing related artists, etc
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@pstumpf commented on GitHub (Feb 7, 2026):

Just tested it. Everything works, except the "Made for You" Playlist, which gives this error:

2026-02-07T09:03:23.675058Z ERROR client_request{request=GetBrowseCategoryPlaylists(Category { id: "0JQ5DAt0tbjZptfcdMSKl3", name: "Made For You" })}: spotify_player::client::handlers: Failed to handle client request: json parse error: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324
2026-02-07T09:03:35.772258Z ERROR librespot_core::session: Connection to server closed.
<!-- gh-comment-id:3863995340 --> @pstumpf commented on GitHub (Feb 7, 2026): Just tested it. Everything works, except the "Made for You" Playlist, which gives this error: ``` 2026-02-07T09:03:23.675058Z ERROR client_request{request=GetBrowseCategoryPlaylists(Category { id: "0JQ5DAt0tbjZptfcdMSKl3", name: "Made For You" })}: spotify_player::client::handlers: Failed to handle client request: json parse error: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324 2026-02-07T09:03:35.772258Z ERROR librespot_core::session: Connection to server closed. ```
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 7, 2026):

Just tested it. Everything works, except the "Made for You" Playlist, which gives this error:

2026-02-07T09:03:23.675058Z ERROR client_request{request=GetBrowseCategoryPlaylists(Category { id: "0JQ5DAt0tbjZptfcdMSKl3", name: "Made For You" })}: spotify_player::client::handlers: Failed to handle client request: json parse error: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324
2026-02-07T09:03:35.772258Z ERROR librespot_core::session: Connection to server closed.

The one you're seeing is https://github.com/aome510/spotify-player/issues/821 and I'm figuring out how to patch it

<!-- gh-comment-id:3863999059 --> @aome510 commented on GitHub (Feb 7, 2026): > Just tested it. Everything works, except the "Made for You" Playlist, which gives this error: > > ``` > 2026-02-07T09:03:23.675058Z ERROR client_request{request=GetBrowseCategoryPlaylists(Category { id: "0JQ5DAt0tbjZptfcdMSKl3", name: "Made For You" })}: spotify_player::client::handlers: Failed to handle client request: json parse error: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324: invalid type: null, expected ID or URI for struct PlaylistId at line 1 column 324 > 2026-02-07T09:03:35.772258Z ERROR librespot_core::session: Connection to server closed. > ``` The one you're seeing is https://github.com/aome510/spotify-player/issues/821 and I'm figuring out how to patch it
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 7, 2026):

@pstumpf https://github.com/aome510/spotify-player/pull/919 fixes the issue. Can you try the latest commit?

<!-- gh-comment-id:3864046968 --> @aome510 commented on GitHub (Feb 7, 2026): @pstumpf https://github.com/aome510/spotify-player/pull/919 fixes the issue. Can you try the latest commit?
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@pstumpf commented on GitHub (Feb 7, 2026):

Yes, that fixes it for me.

<!-- gh-comment-id:3864056415 --> @pstumpf commented on GitHub (Feb 7, 2026): Yes, that fixes it for me.
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@hrkfdn commented on GitHub (Feb 7, 2026):

Hey, I'd love to support this fix, but I was wondering if there's another spotify-player client ID from before all this happened that you can use? Just asking because this one is tied to my personal account 😬

The fix is not only about my client ID but also about how the tokens are fetched in two flows. If you already have a client ID maybe it works with that one as well?

<!-- gh-comment-id:3864104827 --> @hrkfdn commented on GitHub (Feb 7, 2026): Hey, I'd love to support this fix, but I was wondering if there's another spotify-player client ID from before all this happened that you can use? Just asking because this one is tied to my personal account 😬 The fix is not only about my client ID but also about how the tokens are fetched in two flows. If you already have a client ID maybe it works with that one as well?
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@unexist commented on GitHub (Feb 7, 2026):

Thanks for the bypass/fix, works perfectly for me. <3

<!-- gh-comment-id:3864105568 --> @unexist commented on GitHub (Feb 7, 2026): Thanks for the bypass/fix, works perfectly for me. <3
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Feb 7, 2026):

Hey, I'd love to support this fix, but I was wondering if there's another spotify-player client ID from before all this happened that you can use? Just asking because this one is tied to my personal account 😬

The fix is not only about my client ID but also about how the tokens are fetched in two flows. If you already have a client ID maybe it works with that one as well?

Hi @hrkfdn sorry for not asking you before implementing the integration. I wonder how much weight this will add to your client. I can revert the change if needed

I would love to use my own client ID if possible. It’s just I didn’t register for extended quota mode for my client back then so couldn’t use it without losing some functionalities

<!-- gh-comment-id:3864344403 --> @aome510 commented on GitHub (Feb 7, 2026): > Hey, I'd love to support this fix, but I was wondering if there's another spotify-player client ID from before all this happened that you can use? Just asking because this one is tied to my personal account 😬 > > The fix is not only about my client ID but also about how the tokens are fetched in two flows. If you already have a client ID maybe it works with that one as well? Hi @hrkfdn sorry for not asking you before implementing the integration. I wonder how much weight this will add to your client. I can revert the change if needed I would love to use my own client ID if possible. It’s just I didn’t register for extended quota mode for my client back then so couldn’t use it without losing some functionalities
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@ddavisso4 commented on GitHub (Feb 7, 2026):

This seems promising?
https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security

<!-- gh-comment-id:3865157325 --> @ddavisso4 commented on GitHub (Feb 7, 2026): This seems promising? https://developer.spotify.com/blog/2026-02-06-update-on-developer-access-and-platform-security
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@ralph commented on GitHub (Feb 12, 2026):

@ddavisso4 more like the opposite. I'm facing the same issue with Spotifly, my Spotify client for macOS. I've switched it to bring-your-own-client-id, in order to get around these issues.

But users just cannot register a client id! It's supposed to be open again since yesterday, but if just does not work. Spotify really doesn't want any indie developers on their platform any more. 🙁

Image Image
<!-- gh-comment-id:3890438565 --> @ralph commented on GitHub (Feb 12, 2026): @ddavisso4 more like the opposite. I'm facing the same issue with [Spotifly](https://github.com/ralph/spotifly), my Spotify client for macOS. I've switched it to bring-your-own-client-id, in order to get around these issues. But users just cannot register a client id! It's supposed to be open again since yesterday, but if just does not work. Spotify really doesn't want any indie developers on their platform any more. 🙁 <img width="931" height="313" alt="Image" src="https://github.com/user-attachments/assets/816a48f7-e378-4189-ab89-2ade68cfa475" /> <img width="847" height="573" alt="Image" src="https://github.com/user-attachments/assets/505b8543-67ff-45f5-be94-e91e2d74d56a" />
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@CarlosLopezElorduy commented on GitHub (Feb 12, 2026):

I confirm version 0.22.1 fixed it for me 🚀

<!-- gh-comment-id:3891882554 --> @CarlosLopezElorduy commented on GitHub (Feb 12, 2026): I confirm version 0.22.1 fixed it for me 🚀
kerem commented 2026-03-02 23:48:29 +03:00
Author
Owner
Copy link

@pashynskykh commented on GitHub (Feb 12, 2026):

v0.22.1 still now works for me.

I tried removing these paths:

  • ~/.cache/spotify-player/
  • ~/.config/spotify-player/

And reauthenticate after.

Here's the error I get:

Error: try to connect to a client

Caused by:
    0: new session
    1: get credentials
    2: No cached credentials found, please authenticate the application first.
<!-- gh-comment-id:3892677822 --> @pashynskykh commented on GitHub (Feb 12, 2026): v0.22.1 still now works for me. I tried removing these paths: - `~/.cache/spotify-player/` - `~/.config/spotify-player/` And reauthenticate after. Here's the error I get: ``` Error: try to connect to a client Caused by: 0: new session 1: get credentials 2: No cached credentials found, please authenticate the application first. ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
phase2
fix-broken-pipe
v0.0.0
v0.23.0
v0.22.1
v0.22.0
v0.21.3
v0.21.2
v0.21.1
v0.21.0
v0.20.7
v0.20.6
v0.20.5
v0.20.4
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.1
v0.18.2
v0.18.1
v0.18.0
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.2
v0.15.1
v0.15.0
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.1
v0.12.0
v0.11.1
v0.11.0
v0.10.0
v0.9.8
v0.9.6
v0.9.5
v0.9.4
v0.9.3
v0.9.2
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.2
v0.5.1
v0.5.0
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
good first issue

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
third-party

   
third-party

   
wontfix
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
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/spotify-player#535
No description provided.