The same problem here - i am not sure if the api guys are aware of the
consequences every change they make...
On Jul 12, 1:33 am, Mr Blog mrblogdot...@gmail.com wrote:
I have the same problem.
On the App settings it is set to:
Read, Write and Accessdirectmessages
But when users
Hi everyone on the thread,
When you're having this problem, what endpoints are you using for
authentication?
Make sure that you're using https://api.twitter.com/oauth/authorize on the
redirect to Twitter step of OAuth. If you're using
https://api.twitter.com/oauth/authenticate, you'll never be
Hello,
if you refer to the OAuth settings, yes, I have:
OAuth settings
Your application's OAuth settings. Keep the Consumer secret a secret. This
key should never be human-readable in your application.
Access level Read, write, and direct messages
About the application permission
Hi again,
here is what i have set in my Oauth library:
function accessTokenURL() { return 'https://twitter.com/oauth/access_token';
}
function authenticateURL() { return '
https://twitter.com/oauth/authenticate'; }
function authorizeURL() { return 'https://twitter.com/oauth/authorize'; }
On the step where you arrive at Twitter's credential screen, what URL do you
see in the browser bar?
If it's the URL that's being returned by your authenticateURL function, then
it's a URL that can't upgrade your tokens. You want to use the URL returned
in the autorizeURL function instead.
Also,
Hello,
you are right!
I put the api in the front and I changed the authenticate to authorize and
it worked!
thanks - I will refer your twitter username to our app fans!
On 12 July 2011 17:11, Taylor Singletary taylorsinglet...@twitter.comwrote:
On the step where you arrive at Twitter's
I have the same problem.
On the App settings it is set to:
Read, Write and Access direct messages
But when users authenticate with OAuth, it's telling users:
This application will not be able to:
Access your direct messages.
How do we fix this?
On Jul 4, 5:38 pm, alexre...@gmail.com
