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.
When playing a song using the Web Playback SDK (initializing a new device and then sending a play command through the Web API), the playback progress (ie. position) is not reflected on other apps or in the /v1/me/player/ endpoint. The value is stuck on whatever is sent on the initial play request, and only updates when using the .seek() method (which of course interrupts playback for the user). This occurs on any browser.
Here is another topic referencing what seems to be the same issue. https://community.spotify.com/t5/Spotify-for-Developers/currently-playing-returning-incorrect-progre...
For me it doesn't stay at 0. It stays at the position it was last paused at. So there is no playback position update sent from the webapp as it seems.
It seems that the problem has been resolved, at least for me.
Thanks for updating the thread @Straightea.
@sigloasesino are you seeing that the issue has resolved for your app too?
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…