New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing scope in token responses #245
Comments
I have the exact same issue. I've been getting this error since yesterday.
I wonder if it's something Spotify has changed. It's been working for quite some time, and I haven't touched the script at all. |
Yeah, a bunch of our tests broke this morning too... Thanks for reporting this! I hope - as I've done with many of these kinds if issues that it's simply a temporary issue with Spotify. In the event that it's not, we'll fix it. I'm available in 36 hours. Any further info is appreciated! It's a shame this issue affects so much. |
Hello, I did some light digging into this issue. It appears that user authorization is not affected by this only accessing the spotify API via the owners API tokens. The refresh token does not return the scope in the payload. I don't know how much that is necessary but checking if the scope is present in the payload before fixed the error for myself. Although the only time I was using the owners credentials was accessing available genres. This is what I changed:
|
Much appreciated @TrustyJAID! Reading the Authorisation Guide of Spotify, I see no mention of scopes in the client creds flow, though I can't remember whether or not it has been there. The fix would be simple, but there is one complication. It seems that user authorisation without any scopes results in the scope missing from the response as well. So we can't take this to mean "the scope of an app token has been removed because it means nothing". Rather it could mean that "empty scopes are not returned". I think here's what we'll do:
|
A new version has now been released with the fix! I'll leave this issue open for now, and we'll see what Spotify has to say. |
I can't seem to request a client token and this is the error message. Is that due to some API changes cause it did work previously.
The text was updated successfully, but these errors were encountered: