-
Notifications
You must be signed in to change notification settings - Fork 957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spotify web api is ignoring the position param in delete /playlists/{playlist_id}/tracks #1098
Comments
Hi, according to this comment, reordering works again (using the same endpoint), so maybe deleting specific occurrences works too. I'll try that when I get around to it. |
just tried it. it appears spotify is still ignoring the position param sent by playlist_remove_specific_occurrences_of_items() |
Here is an effort to clearly summarize the impact of this api-bug Prior to this Spotify Change After this Spotify Change Example Spotify Web API Documentation Spotipy Code and Documentation |
I think they are trying to make sure that the documentation matches the API. They recently removed an argument that isn't in the documentation for quite a while. Maybe it's the same in this case here. #1107 |
One of the comments in your community post seems to mention UIDs that would identify different items in a playlist. Let's hope this is implemented in the API. Would be a good replacement. I've also contacted Spotify support directly, maybe a moderator will take a look and give us an answer. |
thanks for contacting the moderator. maybe the moderator will contact a spotify employee.... |
summary
playlist_remove_specific_occurrences_of_items(playlist_id, items, snapshot_id=None) uses delete /playlists/{playlist_id}/tracks web api which is currently ignoring the position param in items[{"uri": xxx, "position": xxx}]
here is a link to the spotify dev forum discussing the issue:
https://community.spotify.com/t5/Spotify-for-Developers/Positions-field-in-JSON-body-is-ignored-when-removing-tracks/td-p/6044424
this is the post i put up on the spotify dev forum
removing the position parameter from the web api delete /playlists/{playlist_id}/tracks is a major issue for www.spotifyfinder.com users want to be able to delete a specific duplicate based on position. now that position is being ignored multiple instances of the same track are being removed. this breaks www.spotifyfinder.com i am really hoping that the position parameter is supported once again.
sometimes
sometimes spotify breaks an api and if you wait a couple of weeks spotify will fix the issue. i am hopeful. if the issue gets fixed i will update this issue
The text was updated successfully, but these errors were encountered: