search

spotify / web-api

This issue tracker is no longer used. Join us in the Spotify for Developers forum for support with the Spotify Web API ➡️ https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer
981 stars 79 forks source link

Cannot retrieve recently played tracks accurately #1186

Open ruthiah opened 5 years ago

ruthiah commented 5 years ago

Issue found on Mar 7th 2019.

Endpoint(s):

Steps to reproduce:

  1. Open the API Console
  2. Call the https://api.spotify.com/v1/me/player/recently-played endpoint with limit=50&before=timestamp

Expected behaviour:

Get the recent played tracks from a certain user.

Actual behaviour:

Status code: 200. However the returned tracks don't reflect the most recent ones. Songs are missing during a period of time (a few hours). This happend for 3 times in the past week.

We're building a scrobble service like last.fm and they have a more stable service. If there are any more reliable alternative solutions, would like to learn more.

jscholes commented 5 years ago

Last.fm have access to a websockets-based API as they are a commercial Spotify partner. Perhaps that’s a route you could look at going down.

ruthiah commented 5 years ago

@jscholes The issue is appearing right now. Could you help take a look?

Kaprow commented 5 years ago

Direct calls to the endpoint seem to be having issues: The endpoint "works" but it looks like the resulting "played_at" property is being set to the end time rather than start time and results are delayed even after the track has completed playing. Anyone else seeing this behavior?

I'm pretty sure we saw the same thing in 2017 or '18 and it was determined to be a bug