Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
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
Please provide your feedbacks to proceed further
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?
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
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.
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.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…