Type in your question below and we'll check to see what answers we can find...
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.
due to recent developments, we're again marking this as Fixed.
We've made several backend improvements and from the previous comments those seem to have done the trick for a majority.
For anyone still experiencing this, it looks like the cause is a DNS issue via Chrome - something that's not under our control. All network communication for Spotify goes through the same domain name, so if metadata and playback commands are being sent, the domain is already resolved.
As such, if you're still having issues, please ensure to take the following steps to resolve this:
Shoutout to @danth45 for helping find a solution!