Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Solved! Go to Solution.
Hey David,
I couldn't replicate the issue. I also see the "state_conflict" message but the repeat state is correctly set according to the following API calls. Note that I'm not sending the "device_id" as query parameter, so it will use the user’s currently active device as the target:
/me/player/repeat?state=context // repeat current context
/me/player/repeat?state=track // repeat current track
/me/player/repeat?state=off // turn off repeat mode
Be aware that the repeat state does not work as a toggle. If you want to turn it off, you must send the "state=off" parameter.
Hope it helps!
Hi Alvaron ,
Turn out i find that the error is come from my code there.
the "context" repeat state is 1 instead of 2 actually.
So i think it could be better if you guys can update document here. about the repeat_mode number
https://developer.spotify.com/documentation/web-playback-sdk/reference/#object-web-playback-state
it stated "1" is "once-repeat"
Of course , it would more more ideal if the response can just follow /me/player API.
it just return string instead.
Thanks for your quick reply!
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…