Clearer error when no devices are connected with the currently-playing endpoint

[mikhailusov]

Issue found on January 30th 2018.

Endpoint(s):

• GET /v1/me/player/currently-playing

Scope(s):

• Authenticated user, attempting a call right after successful call 'GET v1/me'

Steps to reproduce:

Not sure, usually happens when I try to call endpoint after not playing for a long time (~ couple of hours?). Or when no devices is available. Tho I am trying to access it while I am running Spotify.

1. Open the API Console
2. Call the currently-playing endpoint with your user after not playing anything in Spotify player for a long time.

Expected behaviour:

200 OK with no data populated, as described on https://beta.developer.spotify.com/documentation/web-api/reference/player/get-the-users-currently-playing-track/.

Actual behaviour:

404 Error (when no device is available or haven't played in a long time) with response body:

{
  "error" : {
    "status" : 404,
    "message" : "non existing id"
  }
}

[bih]

Thanks for the report @mikhailusov! We're investigating this and will report here with updates.

[bih]

Just an update:

The Web API returns the following error message because no devices are connected. After a certain period of time, your main Spotify device (i.e. the desktop app, or mobile app) will also disconnect, which will return this response.

However, I'll leave this ticket open as a feature request for improving the error message. In this case, we agree it is unclear. Once this has been fixed, we'll close the ticket.

[mikhailusov]

Thanks @bih! Also hope documentation will be updated as well.