Multible uris in the Start/Resume a User's Playback

[HuiiBuh]

Issue with multiple song uris in the webplayer

Issue found on January 17th 2020.

Endpoint(s):

• PUT | /v1/me/player/play

Scope(s):

user-modify-playback-state

Steps to reproduce:

1. Open the Spotify Web player (open.spotify.com) and take care that the web player is the active device
2. Open the API Console link
3. Get a OAuth Token 3 Past this in the request body

   {
   "uris": 
   ["spotify:track:4iV5W9uYEdYUVa79Axb7Rh",
    "spotify:track:1301WleyT98MSxVHPZCA6M"]
   }

Expected behaviour:

Play the first track and have the second track in the next up. This is the behaviour observed in the android app and the linux app.
So far this is the only way to add something in the players queue and this is not possible with the Web App from Spotify.

Actual behaviour:

The second uri gets ignored and the next up is full with songs you did not put there.

Context

I want to put some tracks into the playing queue of a user. Currently the only way to do this is to pass multiple uris in the request body. On android and linux this is working great and you can queue songs like that. But in the webplayer only the first uri gets played and the other uris get ignored.... Instead some random songs (added by spotify automatically) are in the next up.

PS: I really appreciate the effort you put into the API. PPS: A Endpoint to modify the queue (retrieve/move songs) would be nice.

[tobika]

I can confirm this. Did the API endpoint specs change?

This has worked for my app in production the last months.

For info: It seems to work when you give and album URI. In this case all the correct tracks are in the queue.

[HuiiBuh]

As I said. It is working if you use the apps... So I should think that this is an issue of the webapp