mirror of
https://github.com/jwilsson/spotify-web-api-php.git
synced 2026-04-27 07:55:49 +03:00
[GH-ISSUE #217] Question about Authorization Code Flow #151
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#151
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 @ghost on GitHub (Jan 24, 2021).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/217
Hi Jonathan,
I'm using the Authorization Code Flow and the code from your example doc.
When I visit
auth.phpI for the first time I am prompted to log into Spotify (testing on a new incognito window). Once logged in I am not presented with a web page listing the scopes and asking the user to authorise them - e.g. like on this screenshot for statsforspotify.com.Instead, I am taken directly to the 'search.php' page which my
callback.phpredirects to.Am I doing something wrong?
Each of the 3 pages are shown below.
Thanks!
Jim
auth.php
callback.php
search.php
@jwilsson commented on GitHub (Jan 24, 2021):
Hey Jim!
I think this might be because you've already accepted the app with those scopes on your Spotify account. You can remove access from your account settings. Or pass the
'show_dialog' => trueoption togetAuthorizeUrl()which will make sure the app approval screen is always shown.@ghost commented on GitHub (Jan 24, 2021):
Thanks Jonathan - I appreciate your patience!
I realise most of the questions I'm asking aren't issues, but more like "how-to" questions. It's very much appreciated that you take the time to respond so quickly and in such a lot of detail.
Thanks again
Jim