omegasolutions wrote:Same issue...
I posted a reply in the wrong thread. I keep screwing up here ;p
My reply was (from:
viewtopic.php?f=30&t=4831&start=10#p28266):
====
martin@rootjazz wrote:Submit logs again, but are your global keys created correctly?
As the issue was the API KEYS as created in apps.twitter.com, were not setup correctly.
IF you also setup your global keys in teh same way, they would have the same issue.
Thanks!
I don't think I'm using global keys. I sent some screenshots though.
I checked the API keys, they all matched. TD also shows OAuth token and secret, but I don't understand where it gets those. I have to manually create them in apps.twitter.com (for the App <random name>). If I copy them back to TwitterDub, it still won't authorise.
When I ran it once more (Generate API Keys + manually copy-pasting the OAuth keys) and go to twitter to check with TD's info, I notice that the API keys are correctly updated BUT the OAuth keys given are from the previous App's APIs.
Copy pasting the manually re-created Oauth keys from twitter to TD doesn't solve it either.
Code: Select all
[code]Oauthverifier:
* FAILED: 097398 : Couldn't get Oauthverifier from URL : https://api.twitter.com/oauth/authorize 200
Please go to the forum post for more help on authorising accounts: http://rootjazz.com/forum/viewtopic.php?f=30&t=1646
[/code]
LOGS: 12891 (was in old thread: 56446; 12891 is without 20k+ log files)