Cannot get callback url's whitelisted

[johnheffernan18]

I’m going through and trying to get the sample web app found at https://github.com/twitterdev/account-activity-dashboard/blob/master/READM.md up and running. I’m having trouble gettting my callback url’s whitelisted.

I’m using Heroku to deploy the app like it says in the read me and keep getting the error

Error: Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

My current setup for the callback url’s is

Any help you can provide is greatly appreciated.

[jessicagarson]

Thanks for reaching out here. I personally worked through a similar issue earlier today.

Have you tried also listing the http versions of these as well. So for you you would have http://tranquil-cliffs-69648.herokuapp.com/callbacks/addsub and http://tranquil-cliffs-69648.herokuapp.com/callbacks/removesub. You also can remove the /webhook/twitter callback link.

You also will want to make sure Sign in With Twitter is enabled.

I hopefully this does the trick. Let me know if you have any further questions.

[johnheffernan18]

Thank you for your response.

We have now set up the Callbacks per your instructions.

Website URL

https://tranquil-cliffs-69648.herokuapp.com/

Sign in with Twitter
Enabled

Callback URL
http://tranquil-cliffs-69648.herokuapp.com/addsub
https://tranquil-cliffs-69648.herokuapp.com/addsub
http://tranquil-cliffs-69648.herokuapp.com/removesub
https://tranquil-cliffs-69648.herokuapp.com/removesub

We are now receiving the errors below when trying to manage subscriptions or receive live activity:

2018-10-16T20:32:23.651432+00:00 app[web.1]: Warning: connect.session() MemoryStore is not

2018-10-16T20:32:23.651449+00:00 app[web.1]: designed for a production environment, as it will leak

2018-10-16T20:32:23.651451+00:00 app[web.1]: memory, and will not scale past a single process.

2018-10-16T20:33:52.257783+00:00 app[web.1]: Error: Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

2018-10-16T20:34:32.073158+00:00 heroku[router]: at=error code=H12 desc=“Request timeout” method=GET path="/socket.io/?EIO=3&transport=polling&t=MP-bTa6&sid=wP9LzhvFXAjTDFJbAAAB" host=tranquil-cliffs-69648.herokuapp.com request_id=b60f19cd-e725-473c-8362-3f6b8c4e1903 fwd=“38.126.138.48” dyno=web.2 connect=1ms service=30000ms status=503 bytes=0 protocol=https

Thank you for your help.

[johnheffernan18]

Thank you for your response.

We have now set up the Callbacks per your instructions.

Website URL

https://tranquil-cliffs-69648.herokuapp.com/

Sign in with Twitter

Enabled

Callback URL

http://tranquil-cliffs-69648.herokuapp.com/addsub

https://tranquil-cliffs-69648.herokuapp.com/addsub

http://tranquil-cliffs-69648.herokuapp.com/removesub

https://tranquil-cliffs-69648.herokuapp.com/removesub

We are now receiving the errors below when trying to manage subscriptions or receive live activity:

2018-10-16T20:32:23.651432+00:00 app[web.1]: Warning: connect.session() MemoryStore is not

2018-10-16T20:32:23.651449+00:00 app[web.1]: designed for a production environment, as it will leak

2018-10-16T20:32:23.651451+00:00 app[web.1]: memory, and will not scale past a single process.

2018-10-16T20:33:52.257783+00:00 app[web.1]: Error: Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

2018-10-16T20:34:32.073158+00:00 heroku[router]: at=error code=H12 desc=“Request timeout” method=GET path="/socket.io/?EIO=3&transport=polling&t=MP-bTa6&sid=wP9LzhvFXAjTDFJbAAAB" host=tranquil-cliffs-69648.herokuapp.com request_id=b60f19cd-e725-473c-8362-3f6b8c4e1903 fwd=“38.126.138.48” dyno=web.2 connect=1ms service=30000ms status=503 bytes=0 protocol=https

Thank you for your help.

[johnheffernan18]

We now have the callback URLs setup the right way and working. We can add and remove subscriptions, but we are still receiving the “request timeout” error. We are having trouble receiving live activity (tweets, retweets, etc).

[LeBraat]

It sounds like your webhook URL might not be validated. You can check this by running the GET :env_name/all/webhooks endpoint.

If your webhook is invalidated, you will have to run this request to manually trigger a CRC - PUT :env_name/webhooks

The live activities should show up in the logs of your web app.

Would you mind explaining what you did to get the callback URLs working properly?

[johnheffernan18]

Dan

I used the following callback urls and they worked. I added the http: url in addition to the https: url.

• https://tranquil-cliffs-69648.herokuapp.com/callbacks/addsub

• https://tranquil-cliffs-69648.herokuapp.com/callbacks/removesub

• http://tranquil-cliffs-69648.herokuapp.com/callbacks/removesub

• http://tranquil-cliffs-69648.herokuapp.com/callbacks/addsub

I am still having trouble showing live activity though. I keep receiving “request timeout” error. The only activity I can see occasionally is when I favorite a tweet that activity will show up in the logs. However, I never receive home timeline updates such as tweets from people I follow.

Thanks for the response

John Hefferna

[LeBraat]

I never receive home timeline updates such as tweets from people I follow.

This is expected. We do not provide home timeline updates via this API. For that, you are going to have to use the GET statuses/home_timeline endpoint.

[system]

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