I uninstalled TD and then re-installed the latest version. Now when attempted to add new accounts I keep getting a message that it's failed Authorization.
I have TD create the app automatically. Then every other acct I try to add fails. I can login to them using TD just fine so I know the user name and pass is correct. I can even create a new app for each account however it will not authorize under a the initial app.
This is what I'm getting:
I had no problems before I reinstalled TD. This is really strange
Also keep getting this in the logs:
Starting: 12/06/2018 21:20 PM
Validating: XXXXXXXXXXXXX No Proxy
procauth: authorise.Process
Attempt login
Login: XXXXXXXXXXXXX : XXXXXXXXXXXXX No Proxy
UA: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Login: get: https://apps.twitter.com/
Already logged in: XXXXXXXXXXXXX
Authorise : XXXXXXXXXXXXX No Proxy
request token: API Consumer key: XXXXXXXXXXXXX API Consumer Secret: XXXXXXXXXXXXX
Generate request: XXXXXXXXXXXXX XXXXXXXXXXXXX
Post requestToken: https://api.twitter.com/oauth/request_token No Proxy
Post requestToken resp: 403 https://api.twitter.com/oauth/request_token No Proxy
* FAILED: request token request: 403
https://api.twitter.com/oauth/request_token
<?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>
* FAILED: 938579832 : Failed request token request
Please go to the forum post for more help on authorising accounts: viewtopic.php?f=30&t=1646
Failed request token request
After Upgrade Failed Authorization
-
- Posts: 6
- Joined: Fri Jun 01, 2018 6:56 am
Re: After Upgrade Failed Authorization
Same problem here. Trying to Authorize an account always results in the following:
https://api.twitter.com/oauth/request_token
<?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>
* FAILED: 938579832 : Failed request token request
Have tried older versions but still the same problem
https://api.twitter.com/oauth/request_token
<?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>
* FAILED: 938579832 : Failed request token request
Have tried older versions but still the same problem
-
- Posts: 6
- Joined: Fri Jun 01, 2018 6:56 am
Re: After Upgrade Failed Authorization
I'm guessing the app hasn't taken into account the new callback url whitelisting requirements: https://developer.twitter.com/en/docs/b ... k_url.html
Can we expect a new version to fix this soon?
Can we expect a new version to fix this soon?
- martin@rootjazz
- Site Admin
- Posts: 34712
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: After Upgrade Failed Authorization
Let me look into this and run some tests here.
- martin@rootjazz
- Site Admin
- Posts: 34712
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: After Upgrade Failed Authorization
https://rootjazz.com/twitterdub/updatetesting.html
in order to authorise to the keys, you must get the CALLBACK URL and specify it for the custom keys, accounts form (or right click to bulk) or global keys via SETTINGS tab
If the app creates new keys, then it will store this url automatically, but for existing keys you need to do it manually
Regards,
Martin
in order to authorise to the keys, you must get the CALLBACK URL and specify it for the custom keys, accounts form (or right click to bulk) or global keys via SETTINGS tab
If the app creates new keys, then it will store this url automatically, but for existing keys you need to do it manually
Regards,
Martin
Re: After Upgrade Failed Authorization
The same error
In apps.twitter.com Setting - Callback Url I write random site but the problem not gone.
Anybody can fix this problem?
In apps.twitter.com Setting - Callback Url I write random site but the problem not gone.
Anybody can fix this problem?
Re: After Upgrade Failed Authorization
using ver 1.4.4.5 and its now working again. Thanks
- martin@rootjazz
- Site Admin
- Posts: 34712
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: After Upgrade Failed Authorization
fixed something else
https://rootjazz.com/twitterdub/updatetesting.html
when creating API APPs from accounts tab wasn't saving callback URL - only if used walk through (and made add account)
https://rootjazz.com/twitterdub/updatetesting.html
when creating API APPs from accounts tab wasn't saving callback URL - only if used walk through (and made add account)
-
- Posts: 6
- Joined: Fri Jun 01, 2018 6:56 am
Re: After Upgrade Failed Authorization
Nice one Martin...working a treat now
- martin@rootjazz
- Site Admin
- Posts: 34712
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact: