mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #930] Using my newly created client_id causes blank UI (429 Too Many Requests) #1495
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kohane27 on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/930
Hello! Hope you're doing well.
Given https://developer.spotify.com/dashboard/create is finally opened again I immediately created an account.
Setting up the Account
APIs usedI ticked allWeb API,Web Playback SDK,Android,iOSand evenAds API.Redirect URIsishttp://127.0.0.1:8989/loginUsage
rm -rf ~/.cache/spotify-playerapp.tomlI copied the new client_idclient_id = "xxx".cargo run -p spotify_player --no-default-features --features pulseaudio-backend,streaming,media-control -j 2.~/.cache/spotify-player/spotify-player-26-02-13-09-06.log:If I removed
client_idinapp.tomlspotify_player works correctly, but I prefer to use my own client_id.I believe this is not spotify_player problem but another problem on spotify side. However, I don't understand why using ncspot's client id works but mine does not. I understand mine does not have "extended quote mode" but I'm the only user. Is there any problem with how I set up spotify app? Maybe we can use this issue to track when we can finally use our own client_id?
Any input is much appreciated. Thank you!
@Spitfire1900 commented on GitHub (Feb 15, 2026):
I've been getting 429s even using the default client_id.
@aome510 commented on GitHub (Feb 16, 2026):
I couldn't create a new app following the new change (even after deleting all my previous apps) so couldn't reproduce the issue myself
To help investigate the issue, can you try to comment these lines
github.com/aome510/spotify-player@83fea36fc7/spotify_player/src/main.rs (L28-L34)and run the app again to see if it fixes rate-limit issue?
I'm not sure if Spotify also applies a stricter rate-limit policy for new user-created app the same way that triggered the previous rate-limit issue with official webapp API
In a related note, I'm looking for a browser cookie integration for API interaction so users don't need to manually create an app or use NCSPOT_CLIENT to interact with Spotify APIs
@klexas commented on GitHub (Feb 17, 2026):
Yeah this is still happening to me also, it's something to do with the Spotify API.
What's confusing is the aome510 are still making new releases when the application is not in a working state ?
@aome510 commented on GitHub (Feb 17, 2026):
It works fine for me without any issues the past few days (with default NCSPOT_CLIENT)
@kohane27 commented on GitHub (Feb 17, 2026):
The default
client_idworks for me but using my ownclient_idstill not working.I'm on the latest commit
8009a68464and have commented out the following:I still have the blank UI with the following log:
spotify-player-26-02-17-09-55.log:Thanks again!
@aome510 commented on GitHub (Feb 18, 2026):
this is the first time I encountered such error and not sure why it happened. Beside that, the log looks normal. Can you search or make any API calls without seeing any 429 error?
@Mcrtin commented on GitHub (Feb 19, 2026):
I've also been getting 429 lately (probably since summer last year ;D)
Before I deleted the cache:
Is there any way I could try and fix this? (maybe get a new api key?)
@aome510 commented on GitHub (Feb 26, 2026):
are you using the latest version of the app, check using
spotify_player --version?@Mcrtin commented on GitHub (Feb 26, 2026):
im using spotify_player 0.22.1 from nixpkgs
@aome510 commented on GitHub (Feb 26, 2026):
hmmm, then I have no idea why you still see the 429 issues
@kohane27 commented on GitHub (Feb 27, 2026):
Probably related: February 2026 Web API Dev Mode Changes - Migration Guide
@kohane27 commented on GitHub (Feb 27, 2026):
Hello! Hope you're doing well.
https://github.com/user-attachments/assets/4095564b-c9a3-43b4-a183-0c7f76e3099d
Searching for anything and entering my playlist lead to infinite "loading" with the following log:
At this point I fully believe it's spotify side's problem that I think there is not much we can do.
@Knightsmarian commented on GitHub (Mar 2, 2026):
made a new fork to address the spotify api changes.
fork: https://github.com/Knightsmarian/spotify-player/tree/spotify-api-feb-2026-migration
Big features; rate limits and cleaned up aliases
spotify api changes if you wanna help: https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide
still broken as of this posting: artist pages, album pages, playlists, radios
you can use your liked list (g y) and search (g s) to get around these broken pages
@SirBrenton commented on GitHub (Mar 2, 2026):
This looks like WAIT (429 + Retry-After) more than anything Spotify-player-specific.
If someone can paste one redacted failure block including response headers (especially Retry-After) we can confirm timing semantics.
Fix shape: a global rate limiter + on-429 “sleep Retry-After (+jitter) then retry” and UI should degrade (render shell + “rate limited, retrying in Xs”) instead of blanking.