Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Continuously getting "User not registered in the Developer Dashboard" auth error
See original GitHub issueDescription
Recently, after Spotify’s new authentication updates regarding apps (you now have an App Status, which can be Development Mode or Granted Quota Extension) I started getting the error User not registered in the Developer Dashboard.
But first, some more info on my application, I have a simple Code Authorization Authentication with one app per user. So before the user is able to use my product, they have to go to the Spotify Dashboard and create a new Dashboard App on THEIR Spotify account, provide my application with a Client Id and Client Secret and then they’ll have a working product.
Now, for any new app made after the Spotify changes, authorization will not work and will fail with the error User not registered in the Developer Dashboard. However, with my old Dashboard App that I’ve had for over 2 years, it does not give this error, I’m assuming this is because it has Granted Quota Extension on that application.
This issue is rather annoying as all my users have manually get a Refresh Token now, which is not a nice solution.
Resolving
I’ve tried resolving this issue but I was unsuccessful, I’m hoping it can be fixed from within this library. Reason Im not reporting this to Spotify is because there are sites that still work with Code Auth and Im assuming it might just be an error in the library, currently I let my users use This Site to manually get a Refresh Token that they can provide my app with.
Links
- My Authorization Code Do note this code still works for apps made before the Spotify change
- Open Spotify Issue with same problem
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I, uh, found the issue; Lets just say I had a facepalm moment
I tried to log in on my alt via an incognito browser, but when the actual verification came that says do you trust this application, I was still logged in on my main, therefore I didnt have permission
All right, I’ll open up my own issue and see how it goes, I’ll close this
Though if you ever know why this error occurs I woud love to know why