Open JoeCotellese opened 5 years ago
Some more information here. I just manually removed some albums from my Spotify library via the desktop application. Re ran the test and it passed.
This was all so I could use it in a python script. I'm rerunning the script and things were chugging along for a while and now have begun to fail again. Is there a limit to the total number of saved albums?
Ok, I just confirmed the limits. I tried to add an album via the desktop application and hit the following error message.
So it seems like the API should properly return when you can't add another album to a library (and also document the limits)
For the benefit of the rest of us, what was the limit you hit, and are you a premium subscriber? I don't think account type affects limits, but it might.
I am a premium subscriber and I believe the limit is 10,000 saved tracks. It's not a hard limit on albums since obviously they have different track lengths.
Spotify really needs to decouple saved albums from saved tracks.
The API team needs to return a more useful error message when you hit this limit.
Hello @JoeCotellese,
Thanks for opening this ticket. I agree that we should be returning a more clearer response than Something went wrong
when you've hit the 10,000 track limit. I'll raise this to the team as a bug.
While we're putting in bug reports, can we file one for the 10,000 track limit?
Ran into the same issue, still would love a better error message than "Something went wrong".
Issue found on 12/18/2018
Endpoint(s):
PUT /v1/me/albums
Scope(s):
Steps to reproduce:
Save Albums for Current User
endpoint with the default album ids in the 'ids' fieldAfter going through the authorization step built into the developer console the API returns and error.
Expected behaviour:
The results as defined by https://developer.spotify.com/documentation/web-api/reference/library/save-albums-user/
Actual behaviour:
502 Server Error (consistently)