Fix invalid scope error when adding a custom Spotify client ID#4182
Merged
Conversation
The OAuth scope list contained three strings that are not valid Spotify scopes: playlist-read, user-modify-private and user-modify. Spotify historically ignored unknown scopes, but newly created Development Mode client IDs now strictly validate them and reject the whole authorization request with an invalid scope error. Remove the invalid scopes; the valid scopes covering the same access (playlist-read-private, playlist-read-collaborative, user-modify-playback-state) were already being requested, so no functionality is lost.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes Spotify OAuth authorization failures for users supplying a custom (Feb 2026 “Development Mode”) Spotify client ID by removing invalid/unsupported scope strings from the requested scope list, preventing Spotify from rejecting the entire auth request with invalid scope.
Changes:
- Remove invalid Spotify OAuth scopes (
playlist-read,user-modify-private,user-modify) from the provider’sSCOPEconstant.
marcelveldt
added a commit
that referenced
this pull request
Jun 13, 2026
anatosun
pushed a commit
to anatosun/music-assistant-server
that referenced
this pull request
Jun 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this implement/fix?
Adding a custom Spotify client ID (developer token) fails during authorization with an
invalid scopeerror. The requested OAuth scope list contained three strings that are not valid Spotify scopes:playlist-read,user-modify-privateanduser-modify. Spotify historically ignored unknown scopes, so this went unnoticed — but newly created Development Mode client IDs (Feb 2026 platform changes) now strictly validate scopes and reject the whole authorization request. Music Assistant's built-in client ID is unaffected, which is why only users supplying their own (recently created) client ID hit this.No functionality is lost — the valid scopes covering the same access (
playlist-read-private,playlist-read-collaborative,user-modify-playback-state) were already being requested.Changes:
playlist-read,user-modify-privateanduser-modifyfrom the Spotify OAuth scope list.Types of changes
bugfixnew-featureenhancementnew-providerbreaking-changerefactordocumentationmaintenancecidependenciesChecklist
pre-commit run --all-filespasses.pytestpasses, and tests have been added/updated undertests/where applicable.music-assistant/modelsis linked.music-assistant/frontendis linked.