You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some combinations of scopes cannot be used together in the Spotify Web API console, if all scopes are being used to generate one a single token, the Spotify endpoint could be rejecting it, but not explicitly.
Perhaps add a force query to /token/{scope}, and store forcefully generated tokens alongside their respective scope inside a unique key-value store in the token manager
The text was updated successfully, but these errors were encountered:
Describe the bug
/web-api/v1/me/player/devices
returns an empty list of devicescurl -X GET
with a token returned from/token
results in the same result, a200 OK
status response, but an empty list of devicesTo Reproduce
http://localhost:24879/web-api/v1/me/player/devices
.{ "devices": [] }
Expected behavior
Expected response:
Result response:
{ "devices": [] }
Version/Commit
v1.6.1
Extra notes
force
query to/token/{scope}
, and store forcefully generated tokens alongside their respective scope inside a unique key-value store in the token managerThe text was updated successfully, but these errors were encountered: