-
Notifications
You must be signed in to change notification settings - Fork 79
https://api.spotify.com/v1/me/player/play doesn't play the specific spotify track_id #631
Comments
I also experience this issue. If I do the following request in the api console here I experience the following: The same happens when I do not provide a Device ID and the tested speaker is already the active speaker. Edit: When using the default PUT Body from the console using the "context_uri" parameter the request does work for the Amazon Echo Dot Device ID: |
+1 Same issue. For me it is able to play music on device (start playback of what ever song/playlist was previously paused) but not start playback of a sent track. |
+1 Also happens here on an Echo Dot or Denon Heos. |
+1 |
+1 However, only experiencing this issue on connect speakers. When I try to play a track on my Macbook (desktop client), everything works fine. Side note: using a |
+1 I am experiencing the same issue with player/play directed at a Spotify Connect device. My PUT request receives a 204 status as expected, but there is no playback. The device receives two consecutive FLUSH commands followed by nothing else: no metadata, no play command, no audio data. More details:
If I send the first PUT request only, it correctly transfers playback to the selected Spotify Connect device. Whatever I was playing on my phone starts playing on that speaker. So I know I have the correct bearer access token in my request header, etc. If I also send the next command to try to play a specific track, everything stops: two FLUSH commands, no audio, as described above. Any help getting this working would be appreciated! |
+1 Fix or a work around desperately needed please! |
+1 Same issue. Playing a simple track does not work anymore. The returned value from the server is 204 yet the track is not played. $ curl \
-D - \
-X PUT "https://api.spotify.com/v1/me/player/play" \
-H "Accept: application/json" \
-H "Authorization: Bearer FOO" \
-H "Content-Type: application/json" \
--data "{\"uris\":[\"spotify:track:4iV5W9uYEdYUVa79Axb7Rh\"]}"
HTTP/2 204
server: nginx
date: Mon, 11 Sep 2017 09:31:56 GMT
cache-control: private, max-age=0
access-control-allow-origin: *
access-control-allow-methods: GET, POST, OPTIONS, PUT, DELETE
access-control-allow-credentials: true
access-control-max-age: 604800
access-control-allow-headers: Accept, Authorization, Origin, Content-Type
x-content-type-options: nosniff
strict-transport-security: max-age=31536000; Work around desperately needed too! |
It is currently working: my previous command works (with the right |
Still not working on an Amazon Echo. The speaker gets marked 'active' but the track doesn't switch. The progressbar (in the desktop app) shows progress yet nothing can be heard. |
+1 Unexpected behavior with Echo Dot and playing tracks. Sending the track id of an already playing track resumes playback and doesnt start it over again. |
Guys, is this likely to be accepted as a bug? It's been quite some time now without any response and is clearly affecting many of us. |
I can imagine its a bug in the embedded spotify connect library on those devices, which makes fixing them require an update from those vendors. Yet still a heads-up and possibly ETA would be nice. |
Hi folks, Thanks for reporting these issues. We're looking into them. @cagriar, which market are you in? It seems the track you mentioned may not be available in the US. Try applying Track Relinking first, or try your request with track id For those experiencing problems on specific devices, we are aware of issues using the Connect API with certain devices and are working to fix it. We will post here with updates. |
Hi @arirawr, I am trying to control a Spotify account registered in Turkish market. I'm quite sure that the track I want to play is available in Turkish market as well. Plus, I can get the track info by using GET track request successfully. So it means its available in Turkish market, right? Do you think that I still need track relinking? |
Hi @arirawr, When I dig deep into track relinking, I have realised that the actual track id that Spotify suggested is the one you have provided in your message. But when I tried to play that track on my Spotify device, it still didn't work. So I re-opened the issue. |
@cagriar Good to know. What type of device are you trying to play on? |
@arirawr It's a device we are implementing that has Spotify hardware partnership. |
Alright, sounds like you may be having the same issue as the other folks with hardware devices then. We'll be sure to post when we have updates on this! |
@arirawr The problem seems solved right now. I am waiting for your updates to close this one. |
I can verify it works on Amazon Echo. I will try Denon Heos as well, thank you so much! |
Verified on Echo Dot and FireTV Stick. Many thanks guys, very much appreciated! |
Thanks, closing the issue. |
Issue found on August 2nd, 2017.
Endpoint(s):
PUT https://api.spotify.com/v1/me/player/play
Scope(s):
Steps to reproduce:
playback/play
endpoint withdevice_id
anduris
body field as:{ "uris": [ "spotify:track:2LlvrdnLa3XbB1b4jYuCnl" ] }
Expected behaviour:
The spotify song with the provided track id specified in the uris field will be started playing on the user device with the id device_id. A successful request will return a 204 NO CONTENT response code.
Actual behaviour:
I get 204 NO CONTENT response but the playback of the user device do not change to the song with the track id provided.
The text was updated successfully, but these errors were encountered: