Skip to content
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

/v1/me/player/devices endpoint does not work through /web-api/ #399

Open
Twinki14 opened this issue Sep 6, 2021 · 0 comments
Open

/v1/me/player/devices endpoint does not work through /web-api/ #399

Twinki14 opened this issue Sep 6, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@Twinki14
Copy link
Contributor

Twinki14 commented Sep 6, 2021

Describe the bug

  • /web-api/v1/me/player/devices returns an empty list of devices
  • Manually calling curl -X GET with a token returned from /token results in the same result, a 200 OK status response, but an empty list of devices

To Reproduce

  • Send a GET request to http://localhost:24879/web-api/v1/me/player/devices.
  • The response body will contain { "devices": [] }

Expected behavior

  • The same response I get using the Spotify Web API console directly, with a generated token from the console for the needed scope
    Expected response:
{
  "devices": [
    {
      "id": "8b55839bcaa2d9c287f56d50bdd44cf18bdc3b7d",
      "is_active": false,
      "is_private_session": false,
      "is_restricted": false,
      "name": "Desktop",
      "type": "Computer",
      "volume_percent": 100
    }
  ]
}

Result response:

{
    "devices": []
}

Version/Commit
v1.6.1

Extra notes

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant