Can't get direct messages? Read, Write and Access direct messages enabled

kurrik · 2011-09-21T22:45:39.000Z

Unfortunately there isn’t a single URL which will accomplish what you want. You can get something close to this flow if you follow these steps:

1.) Use /oauth/authenticate in order to let users “sign in” to the app, which will result in a read/write only token the first time the user signs in.
2.) Once signed in, prompt the user to see whether they wish to enable DMs.
3.) If yes, redirect the user to /oauth/authorize. Once this flow is done, store the new read/write/DM token, and note that the user has enabled DMs in the app data store.
4.) Future “Sign in with Twitter” calls through /oauth/authenticate will return a read/write/DM token.
5.) Check the “enabled DMs” flag in the data store to see whether to prompt the user to upgrade the token, and for any branching logic that requires DM access to be present.

MandeepMehrok · 2011-09-22T06:04:38.000Z

I am also facing problem to get the Direct messages with Xauth approach. I have gone throgh developer kit and suuccessfully get the Direct messages with Oauth approach. But I don’t want to include OAuth approach as it leads to drastic changes to my app(Desktop app).

episod · 2011-09-22T15:07:57.000Z

Direct message access is not available when acquiring access tokens through xAuth.

MandeepMehrok · 2011-09-23T05:34:53.000Z

Thanks Taylor, yup i know this, but i have some areas in my app where i can’t open a browser(an app using different data layer from the original app). Here i am not able to authenticate. I code i have provided the same verifier generated at app level to this app also but failed to authenticate.

MandeepMehrok · 2011-09-23T05:28:59.000Z

Further i am having another problem with oAuth approach, i am not able to change the profile pic as it also fails to authenticate.

armay1219 · 2011-09-23T15:25:26.000Z

What mean you found the good solution of you problem?

BitzBlitzer · 2011-09-27T19:38:23.000Z

Yeah, that’s what I was afraid of. See, now I (as a developer) have to start keeping track of which users I’ve gotten DM access from, so that I can decide whether or not to prompt them.

Maybe there’s a way I can ask Twitter who has DM access? SInce Twitter has to keep track anyway… but this is all kind of a mess, I wish developers just had a single URL they could configure to achieve the desired behavior. Makes me want to move back over to Facebook!

kurrik · 2011-09-27T19:52:11.000Z

Well if you’re keeping track of the user’s token you must have a persistence store. Hopefully adding a bit field into that store isn’t too much of a difficulty. I’ll agree that this isn’t the most direct flow, but it really is more of an exception with the API, not the norm.

The way to determine whether a user has DM access would be to try and load their DM feed - an error response should indicate that the token does not support DMs: https://dev.twitter.com/docs/application-permission-model

BitzBlitzer · 2011-09-27T20:12:40.000Z

It’s not that adding the bit is difficult … it’s the dual maintenance. What if my “belief” that the user has DM access somehow gets out of sync with Twitter’s belief? In fact, this has happened already. Some of my users entered my service AFTER the change was made, so a number of them have DM and I don’t know who.

I’ll guess try the “DM feed load” hack. As for this being an exception vs. norm … we’re talking about authentication and authorization, this is the MOST important thing! If I’m having trouble getting users in the door, all the other bells and whistles don’t really matter.

payaljain32 · 2011-09-30T11:43:40.000Z

log out functionality of twitter app in android app.please help me…its urgent

episod · 2011-09-30T14:38:48.000Z

There’s no “log out” method in the Twitter API. The user controls the access your app has through the authorization screen and app management on twitter.com. What are you needing to “log out” exactly?

MandeepMehrok · 2011-10-01T07:58:35.000Z

Does any one having solution for this or can share some code snippet.

Thanks!

episod · 2011-10-03T14:59:00.000Z

OAuth and xAuth are no different as far as uploading goes. xAuth is but one-step of OAuth.

Here is an example of uploading to the Twitter API correctly: https://github.com/themattharris/tmhOAuth/blob/master/examples/images.php

MandeepMehrok · 2011-10-04T06:14:44.000Z

Thanks @episod for providing me an example, but its in PHP and I am totally blank with PHP.

I am developing the application in .NET(desktop application). Can you provide a link in .NET

Sinister_svk · 2011-10-17T05:29:04.000Z

Hi all!
How long time does it usually takes to update settings from “Read and Write” to “Read, Write and Access direct messages”? I’ve tried to change and wait for about 5 or 6 hours, and all this time my application was inaccessible using neither oauth/authenticate nor oauth/authorize. So I had to rollback application type to “Read and Write” and authentication was fixed.

Cluster_M · 2011-11-30T18:45:33.000Z

getAuthorizeURL($token, FALSE);

Not “true”.

Antkittu · 2011-12-01T06:33:22.000Z

Hi Taylor,
We also updated the application access to:
Read, Write and Access
And Are using “oauth/authorize” for the user-entering-their-credentials step of OAuth
but when getting direct messages it says:
This application is not allowed to access or delete your direct messages

Any thoughts How to resolve with this issue.

ABISimmons2 · 2012-04-14T19:46:08.000Z

I can’t get it to work

denismack · 2012-06-27T14:46:30.000Z

SOLVED: getAuthorizeURL(oauth_token, 0)

vishalshah2012 · 2012-07-27T10:22:17.000Z

it worked perfectly.thanks