Invalid redirect uri after whitelisted redirect uris updated.

[magnusmurel]

Hey, I've logged in to my spotify app many times and know how to make it work. Today I created a new subdomain and updated my redirect uris in my developer dashboard. The subdomain uses excatly the same scripts as my main domain that's still working, but the subdomain gets invalid redirect uri when I try to log in. Can somebody helpe me with this? 🙂

This is my login url

https://accounts.spotify.com/authorize?client_id=xxxx&redirect_uri=https%3A%2F%2Fsub.site.net%2Fspotify%2Flogin%2F&response_type=code&scope=user-follow-modify+user-follow-read  

And I've whitelisted my domain ex: https://sub.site.net/spotify/login/  

my other site with callback https://app.site.net/spotify/login/  is working perfectly

[Hubo]

Hey there, help's here!

Let's have a look here. Hmm, could you try to format the redirect-uri without encoding in your request? ( https://sub.site.net/spotify/login/) Does the same thing happen? Also, could you double-check that you've whitelisted https:// and not http://? Let me know how it goes!

Thanks, have a great day,
Hubo

[magnusmurel]

Hey, after I cleared my head with a walk, i realized I didn't pass the same redirect uri when I asked for the access token after getting the code. I just needed to move my redirect uri definition a little higher in my code.
Thanks for the response 🙂

[Hubo]

Hey there!

A walk always does wonders while coding! Great to hear you’ve got things working. 😄

Have a great week,
Hubo