Some users of my app are reporting that upon entering their credentials at https://api.twitter.com/oauth/authorize (we are also using force login), the authentication flow is quickly interrupted and redirects back to our application without completing the actual authorization. Upon a second attempt, it works as intended.
This only seems to happen for a specific subset of users. Upon further investigation, removing the “www” from the callback URL seemed to solve the problem for some users, but mysteriously it triggered the problem for a new subset of users who weren’t having any issues before.
Anyone have issues with a callback url containing “www”? Or anyone consistently having to authorize the twitter application two times upon a new browser session? Any subsequent attempts to login after the first attempt work perfectly, its odd that the first attempt consistently fails for some of our users.