mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #864] Authentication page pops up every time spotipy.oauth2.SpotifyPKCE() is called #534
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#534
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 @TheMayhem6328 on GitHub (Oct 5, 2022).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/864
Hello! I can't seem to figure out why oauth page pops up every time I call
spotify- trying to use PKCE method to preventclient_secretleak. Here's an example code that I'm runningThis code asks for authentication 4 times - I can see that the token is being cached, but why is the script not using cache and re-authenticating every time? I'm new to Spotipy, Spotify API and anything API really, by the way.
@Peter-Schorn commented on GitHub (Oct 6, 2022):
It looks like there is a bug in which the token info is rejected as invalid if it is not authorized for any scopes. As a workaround, for these endpoints, you can use the
SpotifyClientCredentialsauthorization manager, or authorize for at least one scope.@TheMayhem6328 commented on GitHub (Oct 6, 2022):
Kinda relieved to know that I haven't been doing anything wrong. This is the workaround I found for now:
Still asks for authorization, but now it at least asks for authentication only once per code run instead of every time
spotipy.Spotify()is called@TheMayhem6328 commented on GitHub (Oct 6, 2022):
I overlooked that initially - that works just fine. Thanks for suggesting that!
@TheCheddarCheese commented on GitHub (Apr 28, 2024):
Are there plans for this to be fixed? Is it an issue on Spotify's end?