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

Issue in downloaded Spotify Playlist data from Web API #1080

Open ManognaNampally opened 5 years ago

ManognaNampally commented 5 years ago

HI All,

We observed that the playlist data which is downloaded from Spotify API has some duplicate data. Playlist is downloaded twice which is causing an issue while processing.

Please find some examples in the document attached and let us know if that is normal.

Regards, Manogna Nampally

Issue found on February 19th 2015.

Endpoint(s):

Scope(s):

Steps to reproduce:

  1. Open the API Console
  2. Call the get-users-profile endpoint with user_id %5E

Expected behaviour:

A public user object as described on https://developer.spotify.com/web-api/object-model/#user-object-public.

Actual behaviour:

500 Server Error (consistently)

Duplicate Spotify Playlist Data.xlsx

ManognaNampally commented 5 years ago

Hi All,

Please could you provide us an update on this. This is now severely impacting our business.

Regards, Manogna Nampally

ManognaNampally commented 5 years ago

Hi All,

Please can you give us any update on this. It's been almost three weeks.

Regards, Manogna Nampally

arirawr commented 5 years ago

Hi @ManognaNampally - could you please include information about which API you are calling, with which parameters?

ManognaNampally commented 5 years ago

Hi Ari,

Thanks for the response. Please find the details below and do the needful.

ClientID

URLGetAccess

URLGetFile

c65d2f6b77ef43909ce9b7c065414970

https://accounts.spotify.com/api/token

https://api.spotify.com/v1/

Regards,

Manogna Nampally

SQL Data Support Engineer

1 Bevington Path London, SE1 3PW, UK

[cid:6ADFE95B-EAAE-4018-9EBB-78A4EB3492D0]

From: Arielle (Ari) Vaniderstine notifications@github.com Sent: 22 November 2018 11:30 To: spotify/web-api web-api@noreply.github.com Cc: Manogna Nampally Manogna.Nampally@pias.com; Mention mention@noreply.github.com Subject: Re: [spotify/web-api] Issue in downloaded Spotify Playlist data from Web API (#1080)

Hi @ManognaNampallyhttps://github.com/ManognaNampally - could you please include information about which API you are calling, with which parameters?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/spotify/web-api/issues/1080#issuecomment-441001728, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aqw_hNhxoEqTLxG-bIfCZF-doq9x2gaLks5uxorMgaJpZM4YSpxX.


The information contained in this e-mail and any attachment to it is confidential. It may also contain privileged information and is intended solely for the use of the intended recipient. If you have received it in error, please contact us immediately. If you are not the named addressee, you must not disclose, copy, print, distribute, take any action or rely on it and should notify the sender by reply. You should also destroy the e-mail and its attachments immediately without disclosing its contents to any third party or retaining any copies. The contents of any attachment to the e-mail may contain software viruses, which could damage your own computer system. It is your responsibility to carry out your own virus checks before opening any attachment. [PIAS] cannot be held liable for any loss or damage which occurs as a result of a virus.

viamuli commented 5 years ago

What I've been experiencing so far is that - if the API returns 500 - every single time there was an error/bug in my request parameters (e.g. Querying for a playlist's tracks with offset=100 but total<100 results in HTTP 500 - which should actually be 4xx since the client made the mistake but the server can't handle it). So you should first take a look on your request.

From your initial comment:

Steps to reproduce: Open the API Console Call the get-users-profile endpoint with user_id %5E

Works fine for me in the console (except: do not encode '^' to %5E in the console manually) as well as in a test NodeJS script.

From your last comment:

https://api.spotify.com/v1/

This is not a valid endpoint. Is this URL used in your code? Then a 500 Error is an okay response i guess.