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.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hi,
I'm building a web application using the Web Playback SDK. First of all, I am absolutely thrilled how easy it was to get going with this and the features that it provides. I'm struggling to find information on the following: My web application is supposed to be a long-lived page. After a time of inactivity, the browser may decide to put the tab to sleep, or my computer went into standby and is woken back up. Then the player seems to be broken. Making requests to the Web API that take a device ID, I get "502 Bad Gateway" responses (for the device ID I initially received via the "ready" listener). On the devices endpoint, that device ID is not listed.
My question is: How do I recover from that situation? I don't want to have to refresh the page. I cannot call disconnect() on the player, as that stalls. Calling connect() also stalls. Sometimes, connect() works, I receive the same device ID as before, but still get the 520 Bad Gateway responses. None of the official examples deal with this problem, and I also took a close look at implementations such as https://github.com/y-hiraoka/react-spotify-web-playback-sdk. I didn't find anything that "repairs" a player instance.
Thanks for any advice!