Callback URL not approved - but worked for months

[candrades21]

I have the same problem. I receive the following error from my application log: ’ Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings </ error> </ errors> ’

In my case if I have the application configured as follows:

Callback URL https://www.aguasandinas.cl/web/aguasandinas/c/portal/twitter_login

Callback URL Locked No

Sign in with Twitter Yes

App-only authentication https://api.twitter.com/oauth2/token

Request token URL https://api.twitter.com/oauth/request_token

Authorize URL https://api.twitter.com/oauth/authorize

Access token URL https://api.twitter.com/oauth/access_token

Even so, I’m still receiving the error.

Where is the white list? I understand that putting the URL in the CALLBACK URL section would solve the problem … but no. Could you help me?

[npu3pa4Hblu]

Try adding callback url twittersdk://
It worked for me.

[happycamper]

Hi @dev1showmb What is your use case for using 15 domains in the same app?

[ProZafah]

I am facing the same issue. I have a php script that is being used on multiple domains by multiple users which was working fine until this change.

[Tatters1979]

I’m using the swifter library (https://github.com/mattdonnelly/Swifter) and I’m now facing the same issue. I updated the callback URLs and added the same url callbacks to the URL Schemes in my Xcode Info.plist (minus ://) but I’m still get an error on Auth? The callback documentation says the following?

Please note: Mobile apps with app-specific protocols must use just the protocol. For example, please use example:// as opposed to example://authorize. Any deep linking will result in the following error:

[Smith80D]

What is the whitelist, and how does one add a URL to this? I’m using the rtweet package in R to get tweets using a few different hashtags, for practicing text analysis and for comparing, say, this week’s wordcloud with last week’s, etc, so nothing particularly advanced, but the create_token() function isn’t working, and it seems it’s the recent changes to the OAuth thing. I’m a bit basic when it comes to all of this, and would appreciate any assistance.

[paweljarosz83]

I’m using Java with Spring Social Twitter. I first thought it could be a framework problem, but now I see many guys from other technologies facing the same problem…

[JuanSenosa]

Same problem here. We use dynamic urls for callback. We are currently working on a work around for this issue so we make a callback url in our website then registered the url to apps.twitter.com as callback. We used https://github.com/abraham/twitteroauth for twitter login.

on the code we added the callback url for the oauth_callback parameter but the problem still persist.

[dev1showmb]

Hi @happycamper
In order to get best local SEO position we launch our project with different domains, one per country where we want to be.
Really we use more then 15 domains, around 40.
Our Twitter app is the same for all domains, and before 12th june we could use dynamic Callback without any problem.
Any solution for this issue?
Thank in advance!

[assentyapp]

This might be useful.

As I’ve understood it, it’s a very simple fix to whitelist a callback URL if you already have one set:

1. Simply log in to apps.twitter.com with your Twitter developer account, select your app and click on the Settings tab.

2. Scroll down the page and click on the checkbox to enable the setting “Enable Callback Locking (It is recommended to enable callback locking to ensure apps cannot overwrite the callback url)”

3. Click on the Update Settings button

If done correctly, your settings will be updated as below on the Details tab:

My question is:

• is the above correct? If so, how long should it take for the changes to take effect and for ‘Sign in with Twitter’ to start functioning as normal? Many thanks in advance.

[Connexinet]

Almost instant

[ojm37a]

Yep. Saw the message, updated our callback URLs AND people CAN log in with Twitter. HOWEVER, I’m still getting a bunch of error messages from Twitter saying the callback url is not approved.

Oh, and I CAN’T CHANGE THE CALLBACK URL properly. Our callback url is /index.aspx?sec=log&sub=exa&site=twitter. The callback url setting truncates the url at the first ampersand. How can I save the proper url? I’ve done it once with one of our sites, but I don’t know how…

Please help!!
–Owen

[ojm37a]

Ahh, had to type it in the box like this:
/index.aspx?sec=log%26sub=exa%26site=twitter

Now we’ll see if we keep getting the errors.

[abraham]

Query params are unnecessary for callback URL whitelisting. On the app settings page you can set https://example.com/index.aspx as the callback url and in your OAuth requests https://example.com/index.aspx?cool=param will work just fine.

[ojm37a]

Nope. Still getting the errors…

[_WhyseMan]

Hey. I just want to give everybody a heads up that we should read the documentation in order to understand what’s going on. So I decided to actually read the documentation and there it was. The solution was in the documentation.

On this URL https://developer.twitter.com/en/docs/basics/callback_url there is a sentence that says: "This means that if the callback_url parameter used with the oauth/request_token endpoint isn’t whitelisted, you will receive an error."

So, what I did was, I added a link from my application to the list of “Callback URLs” in my Twitter Application Settings and it worked.

I’m using a npm module Passport.js and there is an option for Twitter Strategy called callbackURL. I have added that URL to the list of Callback URLs in my Twitter Application Settings and it worked immediately.

So now in my “Callback URLs” i have:

• My website’s direct link (https://www.example.com)
• callbackURL from Passport.js (https://webtask-link-0.sandbox.auth0-extend.com/login/twitter/redirect)

And everything is working properly now. I guess that next time we should actually read the documentation before waiting for a solution from someone else.

[Dazzaondmic]

I’ve read the docs and I, like you, am using Passport.js with node. However I have added the callback url from my twitter strategy to my Twitter Application Settings and yet the problem is persisting. I have added a few versions of the url; I’ve changed the domain to be a localhost and the actual IP but nothing is working. Any ideas?

[Talbi_ConSept]

Hello,
Change your callback url here : https://apps.twitter.com/
Not in the new interface
Hope it helps

[rafcolm]

yep, this ^ did the trick!

[LeBraat]