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" <alexre...@gmail.com> wrote:
> Most of my apps require read access forDirectMessages, but they're
> only reading from one account.  Many users DM to one account and I
> need access to that one account to grab all the DMs (which no longer
> works as of June 30th).
>
> I changed the Access Level of all my apps to Read, Write andDirect
> Message, but it doesn't seem that the change has taken place, or I'm
> missing something, somewhere in terms of what I need to do?
>
> When I try and re-authorize an account I see the following on the
> Twitter / Authorize screen:
>
> This application will not be able to:
> Access yourdirectmessages.
> See your Twitter password.
>
> What else do I need to do?  I have confirmed that the application
> settings on Twitter do say, Read, Write andDirectMessagesfor my app
> but I can only use "my access token" (for the Twitter handle
> associated with the app) to accessdirectmessages, anytime I try and
> re-authorize any account through my actual app, I see:
>
> This application will not be able to:
> Access yourdirectmessages.
> See your Twitter password.
>
> ... which isn't inline with how I setup the settings.  Any help would
> be greatly appreciated.  I'm really hoping I'm missing something small
> here.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to