Need help? Check out Spotify Answers for solutions to a wide range of topics. |
hey @spotifyjosh. This seemed to be working perfectly until yesterday. Absolutely nothing has changed in the code from our end. We've checked everything. the client id, secret, scopes, urls.We also are able to get an authorisation code but token swap is failing. Also played around with different accounts but to no avail. I seem to be consistently getting the following error : {'error': 'invalid_request', 'error_description': ''}. What's peculiar is that there is no description. While we are not in the anxious predicament that @ankerbachryhl finds himself in, it is nonetheless frustrating since our dev work has been put on hold.
I am experiencing the same thing since yesterday. We haven't changed anything either. After we get the code from the call to /authorize, I get the following when exchanging it for an access/refresh at /api/token.
{
"error": "invalid_request",
"error_description": ""
}
I can provide some cURLs if that will help with diagnosis.
Hey @rogerchang1 and @rohitganapathy. Are your apps open source? If so, you can link to them in the thread here and I'll take a look. You might also want to try the Glitch sample app that I linked to above. Let me know if this template is not working for you: https://glitch.com/~spotify-authorization-code
I just tried creating another Spotify API App. Which means a new client ID and secret. Still getting the same error. In case that helps
Uhm.
Even de cURL example from the documentation (replaced with correct values) fails with the exact same nondescript error.
Specifically it's the token exchange that fails.
@rogerchang1 wrote:
Could it be possible that react-native-app-auth is passing different parameters to the spotify authorize url causing the code returned to not work?
Yes that could be the problem, @rogerchang1. Spotify does not support PKCE.
@SleeplessByte, welcome to the forum. Which URL parameters did you include in the authorization request URI?