[GH-ISSUE #898] Can't authenticate

kerem commented

2026-03-14 15:10:12 +03:00

Owner

Originally created by @fizz-i on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/898

Problem with authenticating
when i run 'spotify_player authenticate' i get redirected to a web page asked to authenticate by spotify i press continue, then a screen opens 'go back to your terminal :)' in my terminal if i try to use 'spotify_player' it doesn't work
even if you try in a new terminal window.

i think its because my credentials are not getting cached for some reason. because no matter how many time is use
'spotify_player authenticate' it always starts with no credentials cached.

OS: omarchy(arch linux)
Application version: 0.21.2-1

Originally created by @fizz-i on GitHub (Dec 25, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/898 **Problem with authenticating** when i run 'spotify_player authenticate' i get redirected to a web page asked to authenticate by spotify i press continue, then a screen opens 'go back to your terminal :)' in my terminal if i try to use 'spotify_player' it doesn't work even if you try in a new terminal window. i think its because my credentials are not getting cached for some reason. because no matter how many time is use 'spotify_player authenticate' it always starts with no credentials cached. - OS: omarchy(arch linux) - Application version: 0.21.2-1

kerem

2026-03-14 15:10:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 15:10:29 +03:00

Author

Owner

@alex-305 commented on GitHub (Dec 25, 2025):

I'm in the same boat. I also tried creating an api key to authenticate that way and had no luck.

@alex-305 commented on GitHub (Dec 25, 2025): I'm in the same boat. I also tried creating an api key to authenticate that way and had no luck.

kerem commented

2026-03-14 15:10:34 +03:00

Author

Owner

@Cavlon commented on GitHub (Dec 27, 2025):

This is also happening to me on fedora. I successfully authenticate and the device appears in the SwitchDevice panel but selecting it does nothing. I also get no cached credentials found when running spotify_player authenticate. Other devices with music playing also show up but selecting them does nothing.

@Cavlon commented on GitHub (Dec 27, 2025): This is also happening to me on fedora. I successfully authenticate and the device appears in the SwitchDevice panel but selecting it does nothing. I also get no cached credentials found when running spotify_player authenticate. Other devices with music playing also show up but selecting them does nothing.

kerem commented

2026-03-14 15:10:39 +03:00

Author

Owner

@Canonicalize-MK1 commented on GitHub (Dec 29, 2025):

Came to say I am experiencing this issue as well. Tried whitelisting email to ensure access through connect app. One thing I did notice was that when trying to query a song. Was getting a http 429 error: Too many requests. Figured that maybe the client_id value was wrong so I double checked it was correct, wiped the user credentials and access token in .cache. Tried it again. The first link to authenticate had my correct client ID in the link. The second one had a different (what I am assuming is some kind of public client key) one. Tried both cargo and arch installers, neither worked out for me.

@Canonicalize-MK1 commented on GitHub (Dec 29, 2025): Came to say I am experiencing this issue as well. Tried whitelisting email to ensure access through connect app. One thing I did notice was that when trying to query a song. Was getting a http 429 error: Too many requests. Figured that maybe the client_id value was wrong so I double checked it was correct, wiped the user credentials and access token in .cache. Tried it again. The _first_ link to authenticate had my correct client ID in the link. The second one had a different (what I am assuming is some kind of public client key) one. Tried both cargo and arch installers, neither worked out for me.

kerem commented

2026-03-14 15:10:44 +03:00

Author

Owner

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

This might be related to the recent Anna's Archive incident (the 300TB data leak). Spotify has reportedly tightened their API restrictions and rate-limiting to prevent further scraping. This explains the '429 Too Many Requests' errors and the authentication failures we're seeing. We'll probably have to wait until Spotify relaxes these security measures or a workaround is found.

@punjet commented on GitHub (Dec 29, 2025): This might be related to the recent[ Anna's Archive incident](https://annas-archive.org/blog/backing-up-spotify.html) (the 300TB data leak). Spotify has reportedly tightened their API restrictions and rate-limiting to prevent further scraping. This explains the '429 Too Many Requests' errors and the authentication failures we're seeing. We'll probably have to wait until Spotify relaxes these security measures or a workaround is found.

kerem commented

2026-03-14 15:10:49 +03:00

Author

Owner

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

Came to say I am experiencing this issue as well. Tried whitelisting email to ensure access through connect app. One thing I did notice was that when trying to query a song. Was getting a http 429 error: Too many requests. Figured that maybe the client_id value was wrong so I double checked it was correct, wiped the user credentials and access token in .cache. Tried it again. The first link to authenticate had my correct client ID in the link. The second one had a different (what I am assuming is some kind of public client key) one. Tried both cargo and arch installers, neither worked out for me.

Yes i have exactly the same with a different id second time, thought that was the problem at first but maybe not. Tried some workarounds but nothing worked sadly..

@oskarcjohansson commented on GitHub (Dec 30, 2025): > Came to say I am experiencing this issue as well. Tried whitelisting email to ensure access through connect app. One thing I did notice was that when trying to query a song. Was getting a http 429 error: Too many requests. Figured that maybe the client_id value was wrong so I double checked it was correct, wiped the user credentials and access token in .cache. Tried it again. The _first_ link to authenticate had my correct client ID in the link. The second one had a different (what I am assuming is some kind of public client key) one. Tried both cargo and arch installers, neither worked out for me. Yes i have exactly the same with a different id second time, thought that was the problem at first but maybe not. Tried some workarounds but nothing worked sadly..

kerem commented

2026-03-14 15:10:55 +03:00

Author

Owner

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

I had this a similar issue, but I think its because my cache was stale. Running spotify_player authenticate did not help.

I cleared the cache by running:
rm ~/.cache/spotify-player/credentials.json ~/.cache/spotify-player/user_client_token.json
Then I ran spotify_player and it prompted me again to authenticate, but this time it worked

@SireBeef commented on GitHub (Jan 16, 2026): I had this a similar issue, but I think its because my cache was stale. Running spotify_player authenticate did not help. I cleared the cache by running: `rm ~/.cache/spotify-player/credentials.json ~/.cache/spotify-player/user_client_token.json` Then I ran `spotify_player` and it prompted me again to authenticate, but this time it worked

kerem commented

2026-03-14 15:11:00 +03:00

Author

Owner

@klexas commented on GitHub (Jan 21, 2026):

Interestingly this is now failing on the API level.

No cached credentials found, please authenticate the application first.

Error: initialize new Spotify session

Caused by:
0: get credentials
1: Failed to exchange code for access token (Server returned error response: invalid_grant: code_verifier was incorrect)

Even while trying to access the spitify API directly via curl with the correct bearer token there is the error :

{
  "error": {
    "status": 429,
    "message": "API rate limit exceeded"
  }
}

I tried also to create an app in the developer portal and noticed that they have paused all new apps from being added do to improving some reliability. Maybe this is just my account though ?

Seems to me that Spotify have broken their API, intentionally or not I don't know but excluding reverse engineering their client, if the web API is not working, these projects look doomed.

@klexas commented on GitHub (Jan 21, 2026): Interestingly this is now failing on the API level. > No cached credentials found, please authenticate the application first. > Error: initialize new Spotify session Caused by: 0: get credentials 1: Failed to exchange code for access token (Server returned error response: invalid_grant: code_verifier was incorrect) Even while trying to access the spitify API directly via curl with the correct bearer token there is the error : ``` { "error": { "status": 429, "message": "API rate limit exceeded" } } ``` I tried also to create an app in the developer portal and noticed that they have paused all new apps from being added do to improving some reliability. Maybe this is just my account though ? Seems to me that Spotify have broken their API, intentionally or not I don't know but excluding reverse engineering their client, if the web API is not working, these projects look doomed.

kerem commented

2026-03-14 15:11:05 +03:00

Author

Owner

@Spitfire1900 commented on GitHub (Jan 25, 2026):

I've been able to authenticate, but have been unable to list local Devices including locally running Spotify (via snap) or iPhone.

Going to https://developer.spotify.com/dashboard gets the message: "integrations are on hold".

spt is also "mostly" broken and get a "404 Device not Found" error. I actually still have an it registered in my dashboard. I never had to set up spotify_dashboard in my dashboard for it to work previously.

@Spitfire1900 commented on GitHub (Jan 25, 2026): I've been able to authenticate, but have been unable to list local Devices including locally running Spotify (via snap) or iPhone. Going to https://developer.spotify.com/dashboard gets the message: "integrations are on hold". `spt` is also "mostly" broken and get a "404 Device not Found" error. I actually still have an it registered in my dashboard. I never had to set up `spotify_dashboard` in my dashboard for it to work previously.

kerem commented

2026-03-14 15:11:10 +03:00

Author

Owner

@glima commented on GitHub (Jan 27, 2026):

Yeah, this is war by Spotify on non-blessed device IDs, end of an era. So sad.

@glima commented on GitHub (Jan 27, 2026): Yeah, this is war by Spotify on non-blessed device IDs, end of an era. So sad.

kerem commented

2026-03-14 15:11:15 +03:00

Author

Owner

@ricardoprato commented on GitHub (Jan 28, 2026):

same problem here this is the app log after delete cache then execute spotify_player and confirm login

spotify-player-26-01-28-10-24.log

@ricardoprato commented on GitHub (Jan 28, 2026): same problem here this is the app log after delete cache then execute spotify_player and confirm login [spotify-player-26-01-28-10-24.log](https://github.com/user-attachments/files/24911807/spotify-player-26-01-28-10-24.log)

kerem commented

2026-03-14 15:11:20 +03:00

Author

Owner

@glima commented on GitHub (Jan 28, 2026):

Yeah...

2026-01-28T15:25:00.336928Z INFO spotify_player: Starting a client socket at 127.0.0.1:8080
2026-01-28T15:25:00.337203Z INFO spotify_player::media_control: Initializing application's media control event watcher...
2026-01-28T15:25:00.541747Z INFO librespot_core::spclient: Resolved "guc3-spclient.spotify.com:443" as spclient access point
2026-01-28T15:25:00.614221Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:00.615537Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:00.617030Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/playlists: Check settings on developer.spotify.com/dashboard, the user may not be registered.
2026-01-28T15:25:00.619820Z ERROR client_request{request=GetUserSavedShows}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:00.621047Z ERROR client_request{request=GetUserSavedAlbums}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:00.621091Z ERROR client_request{request=GetCurrentUser}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:00.881525Z INFO librespot_connect::spirc: active device is <> with session <2ScCyKPtx8iebS0s0ZRJdI>
2026-01-28T15:25:01.430418Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 403 Forbidden
2026-01-28T15:25:01.430760Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 403 Forbidden
2026-01-28T15:25:03.340196Z INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))), update the context state
2026-01-28T15:25:03.340296Z INFO client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client: Get playlist context: spotify:playlist:5aJTXpbGxFXcRNFhxYyUlD
2026-01-28T15:25:03.405889Z ERROR client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/playlists/5aJTXpbGxFXcRNFhxYyUlD: Check settings on developer.spotify.com/dashboard, the user may not be registered.
2026-01-28T15:25:05.439821Z ERROR client_request{request=GetDevices}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden
2026-01-28T15:25:08.346239Z INFO client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client: Get playlist context: spotify:playlist:5aJTXpbGxFXcRNFhxYyUlD
2026-01-28T15:25:08.409313Z ERROR client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/playlists/5aJTXpbGxFXcRNFhxYyUlD: Check settings on developer.spotify.com/dashboard, the user may not be registered.

and then, at that dashboard: new integrations are currently on hold...

@glima commented on GitHub (Jan 28, 2026): Yeah... 2026-01-28T15:25:00.336928Z INFO spotify_player: Starting a client socket at 127.0.0.1:8080 2026-01-28T15:25:00.337203Z INFO spotify_player::media_control: Initializing application's media control event watcher... 2026-01-28T15:25:00.541747Z INFO librespot_core::spclient: Resolved "guc3-spclient.spotify.com:443" as spclient access point 2026-01-28T15:25:00.614221Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:00.615537Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:00.617030Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/playlists: Check settings on developer.spotify.com/dashboard, the user may not be registered. 2026-01-28T15:25:00.619820Z ERROR client_request{request=GetUserSavedShows}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:00.621047Z ERROR client_request{request=GetUserSavedAlbums}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:00.621091Z ERROR client_request{request=GetCurrentUser}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:00.881525Z INFO librespot_connect::spirc: active device is <> with session <2ScCyKPtx8iebS0s0ZRJdI> 2026-01-28T15:25:01.430418Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 403 Forbidden 2026-01-28T15:25:01.430760Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 403 Forbidden 2026-01-28T15:25:03.340196Z INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))), update the context state 2026-01-28T15:25:03.340296Z INFO client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client: Get playlist context: spotify:playlist:5aJTXpbGxFXcRNFhxYyUlD 2026-01-28T15:25:03.405889Z ERROR client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/playlists/5aJTXpbGxFXcRNFhxYyUlD: Check settings on developer.spotify.com/dashboard, the user may not be registered. 2026-01-28T15:25:05.439821Z ERROR client_request{request=GetDevices}: spotify_player::client::handlers: Failed to handle client request: http error: status code 403 Forbidden 2026-01-28T15:25:08.346239Z INFO client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client: Get playlist context: spotify:playlist:5aJTXpbGxFXcRNFhxYyUlD 2026-01-28T15:25:08.409313Z ERROR client_request{request=GetContext(Playlist(PlaylistId("5aJTXpbGxFXcRNFhxYyUlD")))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/playlists/5aJTXpbGxFXcRNFhxYyUlD: Check settings on developer.spotify.com/dashboard, the user may not be registered. and then, at that dashboard: new integrations are currently on hold...

Rows
Columns

[GH-ISSUE #898] Can't authenticate #1477