spotify / web-api

This issue tracker is no longer used. Join us in the Spotify for Developers forum for support with the Spotify Web API ➡️ https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer
981 stars 79 forks source link

Previous API call raise error 403 #1205

Open Ejay-3D opened 5 years ago

Ejay-3D commented 5 years ago

look similar to https://github.com/spotify/web-api/issues/1038

Issue found on February 19th 2015.

Endpoint(s):

Scope(s):

Steps to reproduce:

  1. Open the API Console https://developer.spotify.com/console/post-previous/
  2. Play a song on a phone or a computer
  3. try the previous API call ( get a valid token first )

Expected behaviour:

Previous track to be played

Actual behaviour:

{ "error": { "status": 403, "message": "Player command failed: Restriction violated", "reason": "UNKNOWN" } }

wolfgangbures commented 5 years ago

Same happens to me with "/play"!! Can't really tell why or since when, probably a few weeks...

MrJJ0ne commented 5 years ago

Same Problem here. Also with the "/play" endpoint.

joosthoi1 commented 5 years ago

same here with /play, /pauze and /previous, strangly not with next

edit: /previous does work, I was making too many requests

edit 2: /play and /pauze do work, you get that error if you try to pauze it if its already pauzed

BenjaminHunt commented 4 years ago

I have the same issue with /play when i try to set the device to the id for my web player.

Edit: I believe this may be because I was requesting spotify to play on the already-active player.

liamtrampota commented 4 years ago

I've found that this happens consistently with particular songs, for instance with trackId 06eGoj25FxAii1L5TxrlQf. Upon investigating further, I found that although that song track info can be found via the spotify api - it's music data is no longer available.