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.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
I figured out my problem, I'm just posting this in case it helps someone else.
I'm not sure if it matters, but I am using the current version of the spotify-ruby gem, and will make this same report there, although I think there is something to learn here for Spotify about how errors could be better reported.
Using the gem, I am obtaining an URL like this:
url = @accounts.authorize_url(scope: scopes)
appears to be a correct oauth authorization URL, but loading it in the browser always results in the subject error (embedded below).
This is an example of the URL:
The problem turned out to be that the "/oauth" part of the URL was incorrect. If I removed that portion, the page loaded fine with the permission flow.
url.gsub!(/\/oauth/, '')
So it looks like the Error page that loads is really a 404 page. It would have saved me some time, and probably a lot of people some time, if that page was more clearly a 404 page and not a vague "something went wrong".