mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #925] show_episodes adding superfluous / to URI #555
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#555
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 @stevereaver on GitHub (Jan 3, 2023).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/925
Describe the bug
When requesting a show list using show_episodes the URI that is used seems to be;
https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes/?limit=50&offset=0
However if the same request is done with a curl the URI used is;
https://api.spotify.com/v1/shows/47Xw6QagBN5lTAp1Cyoyye/episodes?offset=0&limit=20
NOTE: spotipy adds and addtional / after episodes, which breaks the URI and results in a 404
CURL Command
Python Code
Expected behavior
As per description above
Output From Python
Output From CURL
NOTE: The different URI's in each output above.
Environment:
Additional context
Add any other context about the problem here.
@stevereaver commented on GitHub (Jan 3, 2023):
I've spun up my own branch and removed the /, however the error still persists. This has got me really puzzled.
@dieser-niko commented on GitHub (Jan 3, 2023):
Not quite sure why, but if you use SpotifyOAuth (no scopes) instead of SpotifyClientCredentials, it seems to work just fine. So my guess is that this is a problem on Spotifys side.
Also, I made an interesting discovery: when I request a token in the Spotify Developer Console, it asks for the "user-read-playback-position" scope, but it seems to work just fine without scopes. The (obvious) difference is a missing playback position for each episode. Maybe Spotify has restricted access to this endpoint only because of this optional scope, but that's just a theory.
@dieser-niko commented on GitHub (Jan 3, 2023):
And where did you get your token when using cURL?
@stevereaver commented on GitHub (Jan 4, 2023):
The token was generated on the spotify developer console.