Hi there,
We’re currently having an issue with the authorisation request. It seems like the redirect_uri is being ignored and we’re simply getting redirected to the uri at the top of the app’s OAuth redirect URIs list. Our uri is encoded (‘url escaped’) exactly as the example given but it’s not working. Our uri does contain a ? but as it’s encoded would this be an issue? For example our url might be https://website.com/?action=123 which is encoded to https%3A%2F%2Fwebsite.com%2F%3Faction%3D123 but we are redirected to Google’s OAuth Playground because that was at the top of the list in our app settings. Obviously we don’t get an authorisation code and can’t proceed unless I go to the app and swap the list around. Surely this isn’t the expected behaviour?
Thanks,
Mark
Hey Mark! 
It’s a bit tricky to figure out what’s gone wrong exactly, but when we see this behaviour, it usually means we can’t find a redirect URI to use in your OAuth redirect URIs. We’re somehow not picking up the redirect URI you’ve provided, and instead falling back to the one at the top of the list, just as you’ve noticed.
I’ve got a hunch there might be something off with the URL encoding in your redirect URI. If you share your redirect URI, I can dive deeper into this and help find a clearer solution! Feel free to drop me a message! 
Hope this helps and have a great rest of your day!
Fiona
Hi Fiona,
Thanks for your response, it appears I can’t actually send you a message directly (a discourse thing?) so I can’t post you the actual URI here but it’s pretty much as above: https://sub.domain.co.uk/?ACT=123 encoded to https%3A%2F%2Fsub.domain.co.uk%2F%3FACT%3D123 so still none the wiser on what is going wrong?
I ended up just re-ordering the list to get it working.
Thanks again,
Mark
Hey Mark
You should have a message through from me, if you need any more help. I wasn’t sure if you’ve got the problem resolved by re-ordering the list?
Have a great rest of your day! 
Fiona