Closed GabeDahl closed 4 years ago
My current workaround is to manually set the first object's 'start' to 0
Not sure if it's related to this issue, but I noticed that since yesterday several properties are missing from the 'audio-analysis' response. For example, I don't see the confidence property in the last object of the 'bars' array, the 'key_confidence' and 'tempo_confidence' also missing from some section objects. I also don't see the 'start' field in some cases, like you mentioned. Two days ago my client was working without any parsing issues, so I assume it might be a server-side problem?
I just tried a few tests and received the same result in the web console provided at https://developer.spotify.com/console/ Like you say - it must be server-side. Unless they decided to update the API without updating the docs
Thanks for reporting this, folks. We've made some updates and think the issue should be resolved now. If you notice this or another API problem happening again then please let us know over in the Spotify for Developers forum.
Issue found on February 19th 2015.
Endpoint(s):
GET /v1/audio-analysis/{id}
Scope(s):
Steps to reproduce:
Expected behaviour:
An object which includes an array of 'segment' objects. Each segment object should have a key of 'start.' The 'start' key for the first item should have a value of '0'. Repeat with 'sections', 'bars', 'tatums', etc.
Actual behaviour:
An object which includes an array of 'segment' objects. The first object has no 'start' key.