Missing scope in token responses

[felix-hilden]

Hello, since friday the "scope" attribute of token responses has been missing on the client credentials flow and user auth flow without requested scopes.

How should this change be interpreted?

- A temporary hiccup

- A change to the API meaning that all empty scopes are *always* missing from the response instead of being an empty string or null

- A change to the API meaning that empty scopes *may* not be returned

Cheers!

[Hubo]

Hey @felix-hilden, thanks for posting this here.

Hmm, I'd love to take a closer look at what's happening. Are you still having issues here? If I understand the issue correctly: you're requesting a specific scope with the user auth flow or the client credentials flow and the scopes that are granted aren't being returned in the response?

Could you let me know if that's right? Let me know!

Have a great day,
Hubo

[felix-hilden]

I might have miscommunicated by emphasising the wrong information.

What I meant was: with the client credentials flow or the user flow with no requested scopes, the "scope" attribute of the response is missing. Previously I think it was an empty string. A quick fix in code, but I simply wanted to make sure this is intended by Spotify.