topic Re: Regarding Insufficient client scope in Spotify for Developers

Regarding Insufficient client scope

vaigundaanand — Thu, 26 May 2022 09:15:19 GMT

Hi Spotify Team

Greetings, We have integrated your SpotifyiOS SDK for iOS devices based on this documentation https://developer.spotify.com/documentation/ios/quick- start/ and we are facing some inconsistent issues while authorising with the API self.appRemote.authorizeAndPlayURI(“”) and we are receiving the access token through open url delegate call and we set that in configuration as mentioned int the document

After receiving the access token we can able to connect to remote "appRemote.connect()" and while calling this API https://api.spotify.com/v1/me/tracks with the access token we are getting this error for some accounts and for some it’s working fine

error = {
message = "Insufficient client scope"; status = 403;

}

I am mentioning the scope granted for us

playlist-read-private

user-library-read

user-read-private

app-remote-control

user-library-read

Please provide your feedbacks to proceed further

Re: Regarding Insufficient client scope

spotifyjosh — Mon, 30 May 2022 05:47:58 GMT

Hi @vaigundaanand,

Thanks for sharing so many details here. Does the problem go away when the affected users re-authenticate? I noticed that your list included user-library-read twice, is that reflected in your app code too?

Re: Regarding Insufficient client scope

vaigundaanand — Fri, 03 Jun 2022 04:12:25 GMT

As the app is in live we can't make the user to re authenticate and how the re authentication works by connecting to the remote again?

user-library-read is the scope we got permission for and we didn't add it to the code as per the document there is no api to add the scope for the sdk

Re: Regarding Insufficient client scope

vaigundaanand — Fri, 03 Jun 2022 04:14:16 GMT

user-library-read that's a typo I have pasted it twice in the above explanation please provide me the steps how can I resolve this issue

Re: Regarding Insufficient client scope

Squall75 — Wed, 06 Jul 2022 13:43:37 GMT

I was having a similar issue with Web app starting today giving back similar responses where previously it was working for users. Updated scope to include 'user-follow-read' seems to have resolved. Not sure why previous calls to /v1/me/following were working without this scope.

Re: Regarding Insufficient client scope

lerpe — Thu, 07 Jul 2022 15:13:04 GMT

I'm having the same problem. I'm working on a web-app and yesterday I started to get Insufficient client scope error when getting user's saved songs, although before it was working fine and I haven't made any changes in that particular piece of code. I have even gone back to previous commits to see if I have changed something by mistake but I haven't.