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 #817] master build fails to construct app client #488

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

Originally created by @jasht1 on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/817

Describe the bug
The player stopped the audio session suddenly and was not able to create a new librespot session via shift+D. I closed the player and anytime I've tried to launch it since has resulted in :

Error: construct app client

Caused by:
    0: get token for user-provided client
    1: http error: status code 400 Bad Request

To Reproduce
install latest master: cargo install --git https://github.com/aome510/spotify-player.git --features image,notify,fzf
launch: spotify_player

Expected behaviour
should open the client and be able to create a librespot session.

Log and backtrace
Nothing obvious to me in the log and the backtrace was empty.

2025-08-28T18:40:41.109772Z  INFO spotify_player: Configurations: Configs { app_config: AppConfig {<default-conf+my-client_id>} }, Theme { <default-gruvbox_dark>} }, component_style: ComponentStyle { block_title: None, border: None, playback_status: None, playback_track: None, playback_artists: None, playback_album: None, playback_metadata: None, playback_progress_bar: None, playback_progress_bar_unfilled: None, current_playing: None, page_desc: None, playlist_desc: None, table_header: None, selection: None, secondary_row: None, like: None, lyrics_played: None, lyrics_playing: None } }] }, cache_folder: "/home/joeashton/.cache/spotify-player" }
2025-08-28T18:40:41.109943Z  INFO spotify_player::state::data: Loading Playlists data from /home/joeashton/.cache/spotify-player/Playlists_cache.json...
2025-08-28T18:40:41.110341Z  INFO spotify_player::state::data: Successfully loaded Playlists data!
2025-08-28T18:40:41.110351Z  INFO spotify_player::state::data: Loading FollowedArtists data from /home/joeashton/.cache/spotify-player/FollowedArtists_cache.json...
2025-08-28T18:40:41.110477Z  INFO spotify_player::state::data: Successfully loaded FollowedArtists data!
2025-08-28T18:40:41.110483Z  INFO spotify_player::state::data: Loading SavedShows data from /home/joeashton/.cache/spotify-player/SavedShows_cache.json...
2025-08-28T18:40:41.110503Z  INFO spotify_player::state::data: Successfully loaded SavedShows data!
2025-08-28T18:40:41.110509Z  INFO spotify_player::state::data: Loading SavedAlbums data from /home/joeashton/.cache/spotify-player/SavedAlbums_cache.json...
2025-08-28T18:40:41.110631Z  INFO spotify_player::state::data: Successfully loaded SavedAlbums data!
2025-08-28T18:40:41.110642Z  INFO spotify_player::state::data: Loading SavedTracks data from /home/joeashton/.cache/spotify-player/SavedTracks_cache.json...
2025-08-28T18:40:41.152723Z  INFO spotify_player::state::data: Successfully loaded SavedTracks data!

^ this was empty

Environment

  • OS: debian / POPOS
  • Application version: 0.20.7 (built from master)
  • Application features: image,notify,fzf

Additional context
This build was working fine for me yesterday.

Originally created by @jasht1 on GitHub (Aug 28, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/817 **Describe the bug** The player stopped the audio session suddenly and was not able to create a new librespot session via `shift+D`. I closed the player and anytime I've tried to launch it since has resulted in : ``` Error: construct app client Caused by: 0: get token for user-provided client 1: http error: status code 400 Bad Request ``` **To Reproduce** install latest master: `cargo install --git https://github.com/aome510/spotify-player.git --features image,notify,fzf` launch: `spotify_player` **Expected behaviour** should open the client and be able to create a librespot session. **Log and backtrace** Nothing obvious to me in the log and the backtrace was empty. ```spotify-player-25-08-28-19-40.log 2025-08-28T18:40:41.109772Z INFO spotify_player: Configurations: Configs { app_config: AppConfig {<default-conf+my-client_id>} }, Theme { <default-gruvbox_dark>} }, component_style: ComponentStyle { block_title: None, border: None, playback_status: None, playback_track: None, playback_artists: None, playback_album: None, playback_metadata: None, playback_progress_bar: None, playback_progress_bar_unfilled: None, current_playing: None, page_desc: None, playlist_desc: None, table_header: None, selection: None, secondary_row: None, like: None, lyrics_played: None, lyrics_playing: None } }] }, cache_folder: "/home/joeashton/.cache/spotify-player" } 2025-08-28T18:40:41.109943Z INFO spotify_player::state::data: Loading Playlists data from /home/joeashton/.cache/spotify-player/Playlists_cache.json... 2025-08-28T18:40:41.110341Z INFO spotify_player::state::data: Successfully loaded Playlists data! 2025-08-28T18:40:41.110351Z INFO spotify_player::state::data: Loading FollowedArtists data from /home/joeashton/.cache/spotify-player/FollowedArtists_cache.json... 2025-08-28T18:40:41.110477Z INFO spotify_player::state::data: Successfully loaded FollowedArtists data! 2025-08-28T18:40:41.110483Z INFO spotify_player::state::data: Loading SavedShows data from /home/joeashton/.cache/spotify-player/SavedShows_cache.json... 2025-08-28T18:40:41.110503Z INFO spotify_player::state::data: Successfully loaded SavedShows data! 2025-08-28T18:40:41.110509Z INFO spotify_player::state::data: Loading SavedAlbums data from /home/joeashton/.cache/spotify-player/SavedAlbums_cache.json... 2025-08-28T18:40:41.110631Z INFO spotify_player::state::data: Successfully loaded SavedAlbums data! 2025-08-28T18:40:41.110642Z INFO spotify_player::state::data: Loading SavedTracks data from /home/joeashton/.cache/spotify-player/SavedTracks_cache.json... 2025-08-28T18:40:41.152723Z INFO spotify_player::state::data: Successfully loaded SavedTracks data! ``` ```spotify-player-25-08-28-19-40.backtrace ``` ^ this was empty **Environment** - OS: debian / POPOS - Application version: 0.20.7 (built from master) - Application features: image,notify,fzf **Additional context** This build was working fine for me yesterday.
kerem 2026-03-02 23:48:03 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@studentredeemer commented on GitHub (Aug 29, 2025):

This is also happening to me on arch. It was working fine yesterday, then today I get the same error. Overnight, spotify logged me out of all my devices, but I'm unsure if that is related. I tried to re-authenticate and changed my client_id back to the default, but the bug remains.

<!-- gh-comment-id:3237697236 --> @studentredeemer commented on GitHub (Aug 29, 2025): This is also happening to me on arch. It was working fine yesterday, then today I get the same error. Overnight, spotify logged me out of all my devices, but I'm unsure if that is related. I tried to re-authenticate and changed my client_id back to the default, but the bug remains.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@jasht1 commented on GitHub (Aug 29, 2025):

This is also happening to me on arch. It was working fine yesterday, then today I get the same error. Overnight, spotify logged me out of all my devices, but I'm unsure if that is related. I tried to re-authenticate and changed my client_id back to the default, but the bug remains.

I should note I was also logged out of all my devices prior to experiencing this issue, I hadn't mentioned it as I hadn't made any connection, but as we both experienced it it may well be related.

<!-- gh-comment-id:3237790496 --> @jasht1 commented on GitHub (Aug 29, 2025): > This is also happening to me on arch. It was working fine yesterday, then today I get the same error. Overnight, spotify logged me out of all my devices, but I'm unsure if that is related. I tried to re-authenticate and changed my client_id back to the default, but the bug remains. I should note I was also logged out of all my devices prior to experiencing this issue, I hadn't mentioned it as I hadn't made any connection, but as we both experienced it it may well be related.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@belettee commented on GitHub (Aug 30, 2025):

I had the same issue. Like my other clients, spotify_player got logged out. Deleting ~/.cache/spotify-player/credentials.json and going through the login flow again fixed it for me.

<!-- gh-comment-id:3239184777 --> @belettee commented on GitHub (Aug 30, 2025): I had the same issue. Like my other clients, `spotify_player` got logged out. Deleting ` ~/.cache/spotify-player/credentials.json` and going through the login flow again fixed it for me.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@aome510 commented on GitHub (Aug 31, 2025):

Please try the latest version (v0.21.0) to see if the error still persists. I also recommend to delete old token/credentials in the cache folder beforehand

<!-- gh-comment-id:3240506197 --> @aome510 commented on GitHub (Aug 31, 2025): Please try the latest version (`v0.21.0`) to see if the error still persists. I also recommend to delete old token/credentials in the cache folder beforehand
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@javfg commented on GitHub (Sep 1, 2025):

I'm still getting the error in 0.21.0. Not sure if it is a mistake on my side. I've deleted ~/.cache/spotify-player.

Error: construct app client

Caused by:
    0: get token for user-provided client
    1: Failed to read redirect URI from HTTP request

There is indeed no redirect_uri query param in the URL the browser sends back after clicking on continue to the app, only code and state.

<!-- gh-comment-id:3241453614 --> @javfg commented on GitHub (Sep 1, 2025): I'm still getting the error in 0.21.0. Not sure if it is a mistake on my side. I've deleted `~/.cache/spotify-player`. ``` Error: construct app client Caused by: 0: get token for user-provided client 1: Failed to read redirect URI from HTTP request ``` There is indeed no `redirect_uri` query param in the URL the browser sends back after clicking on `continue to the app`, only `code` and `state`.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@JohnOberhauser commented on GitHub (Sep 2, 2025):

I'm still getting the error in 0.21.0. Not sure if it is a mistake on my side. I've deleted ~/.cache/spotify-player.

Error: construct app client

Caused by:
    0: get token for user-provided client
    1: Failed to read redirect URI from HTTP request

There is indeed no redirect_uri query param in the URL the browser sends back after clicking on continue to the app, only code and state.

I'm having this same issue. Deleted the cache as well

<!-- gh-comment-id:3247034496 --> @JohnOberhauser commented on GitHub (Sep 2, 2025): > I'm still getting the error in 0.21.0. Not sure if it is a mistake on my side. I've deleted `~/.cache/spotify-player`. > > ``` > Error: construct app client > > Caused by: > 0: get token for user-provided client > 1: Failed to read redirect URI from HTTP request > ``` > > There is indeed no `redirect_uri` query param in the URL the browser sends back after clicking on `continue to the app`, only `code` and `state`. I'm having this same issue. Deleted the cache as well
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@wiraki commented on GitHub (Sep 3, 2025):

I had the same issue after updating to 0.21 but deleting the cache fixed it.

<!-- gh-comment-id:3248755135 --> @wiraki commented on GitHub (Sep 3, 2025): I had the same issue after updating to 0.21 but deleting the cache fixed it.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@JohnOberhauser commented on GitHub (Sep 4, 2025):

@javfg I was able to get it to work by switching from firefox to chromium. I'm not sure if it was something with firefox itself, or my extensions or the fact I use strict mode.

<!-- gh-comment-id:3255877785 --> @JohnOberhauser commented on GitHub (Sep 4, 2025): @javfg I was able to get it to work by switching from firefox to chromium. I'm not sure if it was something with firefox itself, or my extensions or the fact I use strict mode.
kerem commented 2026-03-02 23:48:04 +03:00
Author
Owner
Copy link

@javfg commented on GitHub (Sep 4, 2025):

That fixed it for me too! Thanks!

<!-- gh-comment-id:3256108255 --> @javfg commented on GitHub (Sep 4, 2025): That fixed it for me too! Thanks!
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#488
No description provided.