Tom, you were right. I thought the app was making the right call to
authorize, but it was somehow making a call to authenticate. All is
working once again!

THANK-YOU!!! :-)

On Jul 4, 4:21 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> 1) Don't use xAuth
> 2) Don't use /oauth/authenticate but /oauth/authorize
>
> Tom
>
> On 7/5/11 1:20 AM, DaveH wrote:
>
>
>
>
>
>
>
> > Twitter Team:
>
> > My application was changed weeks ago to request DM permission. My
> > understanding was all we needed to do was edit the settings for the
> > app, and then re-authenticate the application. Which I did. When I
> > look at the app settings it shows that "Read, Write, Direct Messages"
> > is selected.
>
> > However, when I go to authorize the application, I see that my
> > application will not not be able to access DMs.
>
> > This is a white listed app that needs access to DMs to work. From what
> > I can tell, it should be able to authenticate and get DM access as the
> > application is registered as needed DM level.
>
> > So why is it not being allowed the correct access level?

-- 
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