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...
When invoking the Play API to start playing, the Web Playback will receive play status OK but no sound will be played.
After invoking the Pause API and then the Play API to resume playing, then the play will start from beginning and with sound.
The error seems to be happening only when a new device id is generated,
the Web Playback is working well when using a device id for which there has already been at least one play/pause/resume sequence.
If needed, I can provide the sample calls with CURL to reproduce the issue.
Solved! Go to Solution.
Just found the solution to this issue here:
Having a closer look on the web browser (Chrome) console, the issue seems to be related to the following error:
The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
The Web Playback connect method is invoked on load of the page, hence before user interactions with the page itself...any suggestions on when to call connect or on how to the prevent this error?
Just found the solution to this issue here:
Thanks for updating the thread with the solution you found, @muusic3 🙂
Thank you, this resolved a similar issue I was having on my app.
@Squall75 beware that this might still not working for Safari, in case, check this out too:
Now it is not working in:
MacOS: Ventura 13.3.1+
IOS: 16.4.1+
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…