Error 502 for Transfer Playback request

[gahisee]

Issue found on October 25, 2017.

Endpoint(s):

• PUT /v1/me/player

Scope(s):

• user-modify-playback-state

Steps to reproduce:

1. Open the API Console
2. Call the Transfer a User's Playback endpoint with device id

Expected behaviour:

This error started to appear lately. Earlier this request DID work both with my android app and API Console. As of today, both fail with the same 502 error.

Actual behaviour:

502 Bad Gateway error

[hughrawlinson]

Thanks for the report @gahisee. We'll have a look

[hughrawlinson]

oops

[gahisee]

huh?
first, it's oops, then we'll have a look, now closed?
yet the same 502 error persists.
can someone competent make some sense of this?
hoping for the best...

[hughrawlinson]

@gahisee I accidentally closed the issue, reopened it, and wrote “oops”. The issue has been open since about 5 seconds after I accidentally closed it. I can’t reproduce it with my setup. Can you please tell me what track you’re using, and what devices you’re transferring to and from?

[gahisee]

at the time, no spotify track was playing on the device. it was playing a radio.
so i make the call to "Transfer a User's Playback" and that's when i receive the 502 error.
this is new behavior since it used to work fine.
it seems that it is now a requirement that some track is in playback before the transfer call.
another call that used to work but no longer works is "Start/Resume a User's Playback".

[gahisee]

oh, for "Start a User's Playback", there's no error response.
it simply does not work though.

[hughrawlinson]

Hey @gahisee - what are the devices that you're transferring from and to? When you say the Start a User's Playback endpoint "simply does not work", what http status code do you receive, and can you confirm that there is no response body?

[gahisee]

there is really only one device (Cambridge Audio Network Streamer CXN) on which i'm playing either radio or Spotify. or for more testing, i use the pc desktop running Spotify app and cxn device. by "simply does not work" it means the playback does not occur on the device; i.e., no switching of playback device. the error code was always 502 with body.

here's what i found via testing:

1. transfer-playback call works more consistently if a track is currently playing
2. start-playback call with optional device id seems to work reliably. with this call, i can both transfer the device and start the playback as well.

so far so good.
thanks for your help...

[hughrawlinson]

To confirm, by "radio" you mean like tuner radio, as opposed to Spotify's radio feature? If so, when you're playing radio on the device and you start Spotify playback on the device using the device picker in a Spotify client (Desktop, iOS or Android), does the Network Streamer switch over to Spotify from radio?

the error code was always 502 with body.

What was the content of the body?

start-playback call with optional device id seems to work reliably. with this call, i can both transfer the device and start the playback as well.

We'll continue to monitor for errors in the transfer playback call, but does the start playback call solve your problem?

[ballofpopculture]

I am getting the same issue. With Spotify open, but no track playing, attempting to transfer playback causes a 502 Bad Gateway. Passing the same device id as part of a call to /player/play (i.e. an api call to play a song on a device) the call works correct and plays the song.

In further QAing: it seems that if there is more one than one device, the transfer works correctly, but if there's only one device present, you get the aforementioned Bad Gateway.

[cassiohub]

Think I'm facing the same issue with different users. Find out that 1 out of 50ish requests to this resource return code 502.