July 26:
"Just to repeat what I said in this thread, in case you missed it,
we believe the problem was caused by a recent change in Spotify's api,
which is causing our offline scrobbling solution to malfunction and rescrobble tracks you've already played.
We pushed out a fix for this earlier this week,
which has helped but has unfortunately not fully resolved the issue.
Our team are now working on a second fix,
which I'm hoping (but can't guarantee) will go out before the weekend.
Sorry for any inconvenience this is causing you in the meantime!" (here)
July 25:
July 24:
July 23:
"We've identified a recent change in Spotify's API which is resulting in double scrobbles being submitted (sometimes up to 24 hours later) -- a fix is in progress and should be released soon."
From lastFM:
"Ok, we believe we've identified the issue - a fix is in development and should be available soon.
From what we can tell, Spotify have changed how they report recently played tracks in their API,
which in turn has broken the offline scrobbling logic,
causing it to think that some of the tracks you're playing are offline / cached scrobbles and should be resubmitted.
Basically the timestamp they give us has changed from being the start of the track to the end of the track.
As scrobbling is very much timing dependant (e.g. we have to avoid duplicates while accounting for legitimate repeat plays),
this small change is enough to cause problems,
depending on the length of the track. It's also why the duplicate scrobbles share the timestamp of the following track."
Why so many double scrobbles all of a sudden? Getting pretty irritating.
"Just to repeat what I said in this thread, in case you missed it,
we believe the problem was caused by a recent change in Spotify's api,
which is causing our offline scrobbling solution to malfunction and rescrobble tracks you've already played.
We pushed out a fix for this earlier this week,
which has helped but has unfortunately not fully resolved the issue.
Our team are now working on a second fix,
which I'm hoping (but can't guarantee) will go out before the weekend.
Sorry for any inconvenience this is causing you in the meantime!" (here)
July 25:
- "We deployed a fix two days ago, which should help,
but it seems that it didn't fully address the problem
so it's being looked into again today."
Read more here
July 24:
July 23:
"We've identified a recent change in Spotify's API which is resulting in double scrobbles being submitted (sometimes up to 24 hours later) -- a fix is in progress and should be released soon."
From lastFM:
From what we can tell, Spotify have changed how they report recently played tracks in their API,
which in turn has broken the offline scrobbling logic,
causing it to think that some of the tracks you're playing are offline / cached scrobbles and should be resubmitted.
Basically the timestamp they give us has changed from being the start of the track to the end of the track.
As scrobbling is very much timing dependant (e.g. we have to avoid duplicates while accounting for legitimate repeat plays),
this small change is enough to cause problems,
depending on the length of the track. It's also why the duplicate scrobbles share the timestamp of the following track."
Why so many double scrobbles all of a sudden? Getting pretty irritating.
Comments
Post a Comment