[GH-ISSUE #704] Missing required parameter: redirect_uri #1351

New issue

Closed

opened 2026-03-14 14:30:31 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 14:30:31 +03:00

Owner

Originally created by @daUnknownCoder on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/704

Describe the bug
i cant authenticate the player...

client_id = "a3c5726fcf654d16adaf717a8c798711"
login_redirect_uri = "http://localhost:8888/callback"
client_port = 8888

To Reproduce
spotify_player authenticate
it gives me this link: https://accounts.spotify.com/authorize?response_type=code&client_id=65b708073fc0480ea92a077233ca87bd&state=v5oNw_iGgMw-Z2ko-RrVFw&code_challenge=L4Z7j6UI1ufd
when clearly, my clientid is different, and the config is in ~/.config/spotify-player/app.toml

Expected behaviour
To work ig?

Log and backtrace
Log and backtrace of a run reproducing the bug to help debug the issue, which are usually located in $HOME/.cache/spotify-player/.
spotify_player authenticate
No cached credentials found, please authenticate the application first.
Browse to: https://accounts.spotify.com/authorize?response_type=code&client_id=65b708073fc0480ea92a077233ca87bd&state=v5oNw_iGgMw-Z2ko-RrVFw&code_challenge=L4Z7j6UI1ufd

Screenshots

Environment

OS: Arch Linux
Application version: 0.20.4
Application features: full - spotify-player-full-pipe

Originally created by @daUnknownCoder on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/704 **Describe the bug** i cant authenticate the player... ```rust client_id = "a3c5726fcf654d16adaf717a8c798711" login_redirect_uri = "http://localhost:8888/callback" client_port = 8888 ``` **To Reproduce** `spotify_player authenticate` it gives me this link: `https://accounts.spotify.com/authorize?response_type=code&client_id=65b708073fc0480ea92a077233ca87bd&state=v5oNw_iGgMw-Z2ko-RrVFw&code_challenge=L4Z7j6UI1ufd` when clearly, my clientid is different, and the config is in `~/.config/spotify-player/app.toml` **Expected behaviour** To work ig? **Log and backtrace** Log and backtrace of a run reproducing the bug to help debug the issue, which are usually located in `$HOME/.cache/spotify-player/`. spotify_player authenticate No cached credentials found, please authenticate the application first. Browse to: https://accounts.spotify.com/authorize?response_type=code&client_id=65b708073fc0480ea92a077233ca87bd&state=v5oNw_iGgMw-Z2ko-RrVFw&code_challenge=L4Z7j6UI1ufd **Screenshots** ![Image](https://github.com/user-attachments/assets/cca9ada2-9675-4bbc-8545-2584cc514167) **Environment** - OS: Arch Linux - Application version: 0.20.4 - Application features: full - spotify-player-full-pipe

kerem

2026-03-14 14:30:31 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 14:30:47 +03:00

Author

Owner

@aome510 commented on GitHub (Apr 16, 2025):

The link doesn't seem right. Mine looks like this

when clearly, my clientid is different, and the config is in ~/.config/spotify-player/app.toml

the client_id is correct. The one in your config is only used for Spotify connect while the one in the link is to initiate the application's Spotify client.

@aome510 commented on GitHub (Apr 16, 2025): The link doesn't seem right. Mine looks like this <img width="1728" alt="Image" src="https://github.com/user-attachments/assets/f2e77fe3-8397-40da-9089-a13fe5f2ef83" /> > when clearly, my clientid is different, and the config is in ~/.config/spotify-player/app.toml the `client_id` is correct. The one in your config is only used for Spotify connect while the one in the link is to initiate the application's Spotify client.