[GH-ISSUE #853] Error: construct app client #1447

Closed
opened 2026-03-14 14:57:57 +03:00 by kerem · 2 comments
Owner

Originally created by @MonkyMars on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/853

Describe the bug
When opening the binary installed via either pacman or cargo; it displays:

Error: construct app client

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

And exits

To Reproduce
Opening the installed binary using spotify_player

Expected behaviour
The authentication flow should continue and let me login into my spotify account.

Log and backtrace

2025-10-15T07:20:05.267233Z  INFO spotify_player::state::data: Loading FollowedArtists data from /home/monky/.cache/spotify-player/FollowedArtists_cache.json...
2025-10-15T07:20:05.267248Z  INFO spotify_player::state::data: Successfully loaded FollowedArtists data!
2025-10-15T07:20:05.267252Z  INFO spotify_player::state::data: Loading SavedShows data from /home/monky/.cache/spotify-player/SavedShows_cache.json...
2025-10-15T07:20:05.267259Z  INFO spotify_player::state::data: Successfully loaded SavedShows data!
2025-10-15T07:20:05.267263Z  INFO spotify_player::state::data: Loading SavedAlbums data from /home/monky/.cache/spotify-player/SavedAlbums_cache.json...
2025-10-15T07:20:05.267313Z  INFO spotify_player::state::data: Successfully loaded SavedAlbums data!
2025-10-15T07:20:05.267317Z  INFO spotify_player::state::data: Loading SavedTracks data from /home/monky/.cache/spotify-player/SavedTracks_cache.json...
2025-10-15T07:20:05.270467Z  INFO spotify_player::state::data: Successfully loaded SavedTracks data!

No logs regarding the error I mentioned.

Please refer to this URL for more details.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment
CachyOS
spotify_player 0.21.1
Installed via either cargo or pacman: same error.

Originally created by @MonkyMars on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/853 **Describe the bug** When opening the binary installed via either pacman or cargo; it displays: ``` Error: construct app client Caused by: 0: get token for user-provided client 1: http error: status code 400 Bad Request ``` And exits **To Reproduce** Opening the installed binary using `spotify_player` **Expected behaviour** The authentication flow should continue and let me login into my spotify account. **Log and backtrace** ``` 2025-10-15T07:20:05.267233Z INFO spotify_player::state::data: Loading FollowedArtists data from /home/monky/.cache/spotify-player/FollowedArtists_cache.json... 2025-10-15T07:20:05.267248Z INFO spotify_player::state::data: Successfully loaded FollowedArtists data! 2025-10-15T07:20:05.267252Z INFO spotify_player::state::data: Loading SavedShows data from /home/monky/.cache/spotify-player/SavedShows_cache.json... 2025-10-15T07:20:05.267259Z INFO spotify_player::state::data: Successfully loaded SavedShows data! 2025-10-15T07:20:05.267263Z INFO spotify_player::state::data: Loading SavedAlbums data from /home/monky/.cache/spotify-player/SavedAlbums_cache.json... 2025-10-15T07:20:05.267313Z INFO spotify_player::state::data: Successfully loaded SavedAlbums data! 2025-10-15T07:20:05.267317Z INFO spotify_player::state::data: Loading SavedTracks data from /home/monky/.cache/spotify-player/SavedTracks_cache.json... 2025-10-15T07:20:05.270467Z INFO spotify_player::state::data: Successfully loaded SavedTracks data! ``` No logs regarding the error I mentioned. Please refer to [this URL](https://github.com/aome510/spotify-player?tab=readme-ov-file#logging) for more details. **Screenshots** If applicable, add screenshots to help explain your problem. **Environment** CachyOS spotify_player 0.21.1 Installed via either cargo or pacman: same error.
kerem 2026-03-14 14:57:57 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@sebvu commented on GitHub (Oct 16, 2025):

I would look at the 'solution' comment posted in #837

https://github.com/aome510/spotify-player/issues/837#issuecomment-3321454295

I do not know if it's the recommended solution since everyone has their own specific issues, but it worked for me.

<!-- gh-comment-id:3408676032 --> @sebvu commented on GitHub (Oct 16, 2025): I would look at the 'solution' comment posted in #837 https://github.com/aome510/spotify-player/issues/837#issuecomment-3321454295 I do not know if it's the recommended solution since everyone has their own specific issues, but it worked for me.
Author
Owner

@ElphaTech commented on GitHub (Oct 19, 2025):

It also worked for me. Just do rm -rf ~/.cache/spotify-player and then run spotify_player again. It will prompt you to login again.

<!-- gh-comment-id:3419934535 --> @ElphaTech commented on GitHub (Oct 19, 2025): It also worked for me. Just do `rm -rf ~/.cache/spotify-player` and then run spotify_player again. It will prompt you to login again.
Sign in to join this conversation.
No milestone
No project
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#1447
No description provided.