Internal server error when using PUT /v1/me/player/pause or play

[Oldes]

Issue found on July 1st 2020.

Endpoint(s):

• PUT /v1/me/player/pause
• PUT /v1/me/player/play

Scope(s):

• user-modify-playback-state

Steps to reproduce:

1. goto https://developer.spotify.com/console/put-pause
2. request token and play some music in browser
3. try the demo

Expected behaviour:

Music stops or resumes.

Actual behaviour:

{
  "error": {
    "status": 500,
    "message": "Server error."
  }
}

Sometimes the response is:

{
  "error": {
    "status": 404,
    "message": "Player command failed: No active device found",
    "reason": "NO_ACTIVE_DEVICE"
  }
}

In such a case I must pause and resume the music in browser manually, to get it working.

Also when using the curl example how it is on the console page from command line (with valid token), the response is Error 411 (Length Required). The reason is, that it seems to require Content-Length in the header even when there are no data send.

[Oldes]

PUT https://api.spotify.com/v1/me/player/seek has the same issue.

[Oldes]

Also when I do GET /v1/me/player/devices, and I have a list of them....

{
  "devices" : [ {
    "id" : "8fe3...83a",
    "is_active" : true,
    "is_private_session" : false,
    "is_restricted" : false,
    "name" : "Web Player (Chrome)",
    "type" : "Computer",
    "volume_percent" : 41
  } ]
}

Using:

PUT /v1/me/player/volume?volume_percent=10&device_id=8fe3...83a

returns 404 Not Found and than when I repeat GET /v1/me/player/devices, I get just empty result:

{
  "devices" : [ ]
}

I must again stop and resume playback in browser to get the list back. This must be related to: https://github.com/spotify/web-api/issues/1582

[Oldes]

It seems to be OK today!

[Oldes]

It happens again! :-(

[joshubrown]

Hey @Oldes! Sorry to hear about the trouble that you are having here. Would you mind creating a topic over in the Spotify for Developers forum? We no longer use this issue tracker.

[Oldes]

Hi @joshubrown, I don't understand, how the forum can be better than real issue tracker, but anyway.. it is there, in a very short variant, just linking here.

Strange is, that the mentioned PUT methods work again today... so maybe it's just occasional issue.