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.
Plan
Premium
Country
USA
Device
iPhone 11 Pro
Operating System
iOS
My Question or Issue
We are authenticating with the Spotify app but get the following URL callback:
smoresapp://spotify-login-callback/?spotify_version=8.7.38.1353#error=invalid_scope
This only started happening today, one day after we got our quota extension approved.
Before, it was working fine. Before we had the quota extension, we were working with specific accounts (from Users and Access) that were approved.
For what it's worth here are the scopes we are using, although this error also happens even when I pass in an empty array for scopes (i.e. no scopes)!
Current scopes:
"user-read-private", "playlist-modify-public", "playlist-read-private", "playlist-modify-private", "user-follow-read", "user-library-modify", "user-library-read", "user-top-read"
I have deleted our app (Smores) from my device, I have deleted Spotify from the device, I've removed Smores from my Account (under Apps) etc. I think I ensured I'm starting with a clean slate.
Looking forward to your thoughts.
Thanks!
Could this be related to this?
Fwiw this is a blocker for us since we can’t even test the app anymore.
We've reviewed this and according to the logs your client id is requesting two additional scopes: user-read-email and app-remote-control.
If you're using the iOS SDK you always need the app-remote-control scope.
You can submit a scope extension request via the Developer Dashboard to get the scopes added to your app.
Appreciate the reply – indeed it looks like adding app-remote-control fixed it. We've requested an extension to get that permission too.
user-read-email was just to see what happens when we ask for more scopes.
Thanks again!
P.S. Maybe there's a way to have the Spotify library return the missing scope? Now that you mention it, it's clear, but it would have saved 3 days if Spotify could have called us back with just `?missing_scope=app-remote-control` or something like that. Either way, thanks for the reply!
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…