[GH-ISSUE #934] INVALID_CLIENT: Invalid redirect URI #1496

Open
opened 2026-03-14 15:15:28 +03:00 by kerem · 0 comments
Owner

Originally created by @SHINEXMAN on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/934

Hi! i have an issue with authorization

I am unable to complete the authentication process for spotify_player on macOS Sequoia (Homebrew install). Despite configuring a custom Client ID and ensuring that the Redirect URIs in the Spotify Developer Dashboard exactly match my local app.toml, the app fails to receive the authorization code. When I launch the player, it correctly prompts me to authenticate and opens a browser window. However, after I enter my credentials and click authorize, a second window immediately opens with the error "INVALID_CLIENT: Invalid redirect URI."

I have verified that I am using the 127.0.0.1 instead of localhost to comply with recent Spotify API changes, and I have confirmed that the port and callback path are identical in both the dashboard and the config file. It appears the application is either failing to bind to the local port on Sequoia or there is a mismatch during the secondary redirect handoff. I have been attempting to resolve this for several days without success and would appreciate any help

Originally created by @SHINEXMAN on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/aome510/spotify-player/issues/934 Hi! i have an issue with authorization I am unable to complete the authentication process for spotify_player on macOS Sequoia (Homebrew install). Despite configuring a custom Client ID and ensuring that the Redirect URIs in the Spotify Developer Dashboard exactly match my local app.toml, the app fails to receive the authorization code. When I launch the player, it correctly prompts me to authenticate and opens a browser window. However, after I enter my credentials and click authorize, a second window immediately opens with the error "INVALID_CLIENT: Invalid redirect URI." I have verified that I am using the 127.0.0.1 instead of localhost to comply with recent Spotify API changes, and I have confirmed that the port and callback path are identical in both the dashboard and the config file. It appears the application is either failing to bind to the local port on Sequoia or there is a mismatch during the secondary redirect handoff. I have been attempting to resolve this for several days without success and would appreciate any help
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#1496
No description provided.