mirror of
https://github.com/jwilsson/spotify-web-api-php.git
synced 2026-04-27 07:55:49 +03:00
[GH-ISSUE #263] Sometimes adding twice the track to the playlist #190
Labels
No labels
bug
docs
enhancement
enhancement
enhancement
feedback wanted
good first issue
help wanted
help wanted
help wanted
invalid
pull-request
question
question
upstream
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-web-api-php#190
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @upgrader-dev on GitHub (Jun 19, 2023).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/263
Hello,
I'm sometimes experiencing a double add of the track in the playlist.
My ´auto_retry' is set to off...
It looks like when the server response is getting late there is a second try and both lead to successfully adding the track to the playlist.
I have no evidence about that, that's just my idea.
Did anyone already encountered that behavior?
Thanks
Benjamin
@jwilsson commented on GitHub (Jun 19, 2023):
Hey!
The
auto_retryoption only controls whether or not to retry requests when you hit the Spotify API rate limit. There's no other retry functionality in this library.I suspect it's something on Spotify's end that's the issue. I'd post an issue at their Developer Forum and see if anyone else has experienced the same issue.
@upgrader-dev commented on GitHub (Jun 19, 2023):
Ok thank youEnvoyé de mon iPhoneLe 19 juin 2023 à 20:49, Jonathan Wilsson @.***> a écrit :
Hey!
The auto_retry option only controls whether or not to retry requests when you hit the Spotify API rate limit. There's no other retry functionality in this library.
I suspect it's something on Spotify's end that's the issue. I'd post an issue at their Developer Forum and see if anyone else has experienced the same issue.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>