For our application we recently realized we’re going to need to raise our Access Level from read-only to read-write. The problem is that after the access level was increased to read-write, users became unable to complete the authentication process if they have already gone through it before.
Twitter will require users who agreed to read-only to accept the new terms of the application at api.twitter.com/oauth/authenticate. Those users who have never added the application before can continue just fine. However, those who had previously agreed to read-only instead get stuck on that Authorize page forever. It simply posts to itself and never redirects successfully.
Is this a Twitter bug, or something else anyone is aware of? The only solution I have found so far is to simply reduce the Access Level back to read-only. I can also authorize with a given account in this bugged state if I first revoke permissions to the application.