[twitter-dev] Re: Bug with the new DM authorization and the /oauth/authenticate method
I have exactly the same problem; I changed the settings for my app to RWD, but when going through the oAuth flow the app still says it can't access direct messages (and I get a 93 error). Screenshots: http://moby.to/cn9dtw I have many users of my app. Hope this will be fixed soon. Michiel On Jul 1, 12:41 am, Laurent Quérel laurent.que...@yoono.com wrote: Hi all, My twitter app (a firefox/chrome extension in 'browser mode') uses the method /oauth/authenticate in the oauth process. I changed the access level of my app to read, write direct messages to conform to the new rules about DM access. I observe an error 93 when the application try to read DM and the authenticate page continue to display that my app has no access to DM... If I replace /oauth/authenticate by /oauth/ authorize this issue disappears. Is it normal? Laurent -- 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
[twitter-dev] Re: Bug with the new DM authorization and the /oauth/authenticate method
Erm DM access is only granted from /oauth/authorize now as was stated by Matt here http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e954fc0f8b5aa6ec/a608900f722416b7?q=dmlnk=nl; The R/W/DM permission can only be granted through the /oauth/ authorize route. Sign in with Twitter cannot be used to grant R/W/DM. And here https://dev.twitter.com/pages/application-permission-model-faq You said you were restricting this permission to the OAuth /authorize web flow only. Will /oauth/authenticate (Sign in with Twitter) support the new permission? The R/W/DM permission can only be granted through the /oauth/authorize route. Sign in with Twitter cannot be used to grant R/W/DM. On Jun 30, 11:41 pm, Laurent Quérel laurent.que...@yoono.com wrote: Hi all, My twitter app (a firefox/chrome extension in 'browser mode') uses the method /oauth/authenticate in the oauth process. I changed the access level of my app to read, write direct messages to conform to the new rules about DM access. I observe an error 93 when the application try to read DM and the authenticate page continue to display that my app has no access to DM... If I replace /oauth/authenticate by /oauth/ authorize this issue disappears. Is it normal? Laurent -- 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
[twitter-dev] Re: Bug with the new DM authorization and the /oauth/authenticate method
I had the same problem, I asked @twitterapi they said it usually takes some time before it actually saves the permissions. Mine was reverting back to read only. Just keep trying. -- 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
