Setting permissions from read to read/write/direct message returning 500 error from twitter auth


#1

I’m trying to change the permissions on one of our twitter apps. Once I set the permissions from read only to read/write/direct message, every attempt to authenticate via oauth(https://api.twitter.com/oauth/authenticate) is giving a 500 page from twitter stating “Something is technically wrong.
Thanks for noticing—we’re going to fix it up and have things back to normal soon.”

Once I set the app back to read-only I’m able to authenticate.

I’ve also set up a fresh test app, with initial settings for read only – I’m able to authenciate, once I set it to read/write/direct messages I’m also able to log in.

It seems that this issue is only affecting the original twitter app.

Any help/insight would be greatly appreciated.
Thanks.


#2

We’re experiencing the exact same issue. Also tried regenerating the keys to no avail.