Needs to Fix/Add/Re-approve Scopes

[mashmia]

I am having an issue with several users that they are not able to successfully achieve their desired action.

Here is the error that appears in my logs:

HTTP Error for POST to https://api.spotify.com/v1/users/xxx(user_name)/playlists with Params: {} returned 403 due to Insufficient client scope

My inkling is that these users didn't complete the scope permissions process. Perhaps they logged into the Spotify redirect page. Now their user_id is recognized etc and they are technically logged into my app, but they still need to approve scopes.

Now, if they redirect to the Spotify page, they log in and don't have the opportunity to approve scopes. It seems as if their decision is stored. 

[Ximzend · Accepted solution]

One thing you can try is to set "show_dialog" to true, as explained at this page.

[SpotifyTom]

Sounds like you're missing the playlist-modify-private and/or the playlist-modify-public scope on the user's access token.

You will need to recreate the user's token to add these scopes by taking them through the authorization flow once again with the correct scopes. They should be automatically prompted with the dialog during this as the scopes have changed.

[mashmia]

This was the problem. A couple of users exited the Spotify redirect before they could approve the scope permissions.

[mashmia]

Actually, the problem persists. The show_dialog suggestion was a good step and did what I thought it would do. However I misdiagnosed the problem that is the discussion topic. I will start a new topic.