#1

Hi there,

I’ve got a weird problem and I didn’t find any solution to fix it.

I’ve created an app with the “Sign in with Twitter” option checked to allow user to sign/register via their Twitter account.

I’ve whitelisted all the callbacks uri (for local, dev and prod environment)

It works great on local and dev but not on production. Here is the error:
<?xml version='1.0' encoding='UTF-8'?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>

I’m using Laravel and the Socialite Package, did anyone solve this ?

Thanks

#2

I’ve had problems where I’ve added the correct callback URL to a Twitter app but forgot to modify the path to request so it wasn’t getting sent to the OAuth flow correctly. Could you log/inspect the requests that include the callback URL to Twitter’s endpoints?

1 Like
#3

The redirect function from Socialite returns this:

HTTP/1.0 302 Found
Cache-Control: no-cache, private
Date:          Thu, 12 Mar 2020 08:05:45 GMT
Location:      https://api.twitter.com/oauth/authenticate?oauth_token=TubJhgAAAAABCdF2AAABcM3HJrI

<!DOCTYPE html>
<html>
    <head>
        <meta charset="UTF-8" />
        <meta http-equiv="refresh" content="0;url='https://api.twitter.com/oauth/authenticate?oauth_token=TubJhgAAAAABCdF2AAABcM3HJrI'" />

        <title>Redirecting to https://api.twitter.com/oauth/authenticate?oauth_token=TubJhgAAAAABCdF2AAABcM3HJrI</title>
    </head>
    <body>
        Redirecting to <a href="https://api.twitter.com/oauth/authenticate?oauth_token=TubJhgAAAAABCdF2AAABcM3HJrI">https://api.twitter.com/oauth/authenticate?oauth_token=TubJhgAAAAABCdF2AAABcM3HJrI</a>.
    </body>
</html>
#4

If you’ve already reviewed the Laravel Socialite configuration guide, you could reach out to the Laravel community for support: https://laracasts.com/discuss

#5

Did you get anywhere with this. I have the same problem.
Sadly Im not a php dev and the code I have is in php so cant step through etc
Definitely have correct callback in place and can not find any other place to white-list the callbacks like in Facebbok apps.
Was it in your code or a twitter issue?

#6

It was probably a Twitter issue, I created a new app and whitelisted the same callback and it works now…

Maybe try to create a new app first and tell me if it worked for you.

#7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.