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
983 stars 79 forks source link

Audio Analysis: HTTP 404 Not Found #1570

Closed nicolasanjoran closed 4 years ago

nicolasanjoran commented 4 years ago

Issue found on May 5th 2020.

Endpoint(s):

Scope(s):

Steps to reproduce:

  1. Open the API Console
  2. Call the audio-analysis endpoint.
  3. Try with the default track ID.

Expected behaviour:

The audio analysis should show up.

Actual behaviour:

404 Not found

{
  "error": {
    "status": 404,
    "message": "analysis not found"
  }
}
nicolasanjoran commented 4 years ago

After some more trials, it seems that it doesn't work for most of the songs. However, for some of them, the analysis is retrieved. I tried using a VPN to see if its a local issue, but it doesn't impact the results, the API returns the same results for all VPN locations.

Example of a working ID: https://api.spotify.com/v1/audio-analysis/1wjzFQodRWrPcQ0AnYnvQ9

Example of an ID that doesn't work: https://api.spotify.com/v1/audio-analysis/06AKEBrKUckW0KREUWRnvT

Tinouga commented 4 years ago

Same as you, I receive the audio analysis for maybe 1 in 20 songs (getting 404 for the rest).

njm222 commented 4 years ago

I am also having the same issue with the endpoint. Looks like a duplicate issue #1555

nicolasanjoran commented 4 years ago

@njm222 no it's not a duplicate.

10 days ago, the audio-analysis endpoint started to send json files with missing attributes, this is what the issue #1555 is about. The new issue I opened is about the analysis not being retrieved using the endpoint, which results in a HTTP 404.

Tinouga commented 4 years ago

@njm222 no it's not a duplicate.

10 days ago, the audio-analysis endpoint started to send json files with missing attributes, this is what the issue #1555 is about. The new issue I opened is about the analysis not being retrieved using the endpoint, which results in a HTTP 404.

Yeah and the #1555 can be solved using default values, this one is another matter :|

nicolasanjoran commented 4 years ago

For information, I started to get 404 errors ~10h ago if that's helpful (at 3am GMT+2).

MadalenaSousa commented 4 years ago

Just leaving a comment because I'm having the same issue

Tinouga commented 4 years ago

It seems to be working now, I'm not getting any 404 anymore (tested with a few tracks that were giving me this error).

nicolasanjoran commented 4 years ago

It seems to be working now, I'm not getting any 404 anymore (tested with a few tracks that were giving me this error).

Same here, I was just waiting for a few minutes before closing the issue, just in case.