spotify-web-api-node icon indicating copy to clipboard operation
spotify-web-api-node copied to clipboard

Published 20 hours ago • verified publisher icon thelinmichael

Need to manually interact with spotify first, otherwise returns 404: Not Found

Open fartbender opened this issue 4 years ago • 4 comments

When I open a player and send a play request it returns 404: Not found. After manually starting a song in the player, I can again control it, but if nothing has played for a while the error returns, even though the player has stayed open.

fartbender avatar Sep 24 '20 14:09 fartbender

Hi @fartbender. Thanks for opening this issue.

If I understand you correctly, the application you're building using this wrapper doesn't work properly until you've interacted with the official Spotify client. Is this correct?

thelinmichael avatar Sep 27 '20 11:09 thelinmichael

Hi there - That is correct. I should probably say that I am building it using Node-red

fartbender avatar Sep 27 '20 11:09 fartbender

I have the same issues

neonstorm13 avatar Oct 16 '20 01:10 neonstorm13

We encounter the exact same issue for a few weeks now. We have a NodeJS service in our backend which uses the spotify web api to play/stop songs. We always receive a [Error [WebapiError]: Not Found] error until we start/stop a song manually in the Spotify Player. After that the play/stop command works for a few minutes without any issues.

xadh00m avatar Jun 30 '21 09:06 xadh00m