A user of our application reports they are unable to sign in with Twitter. The application correctly redirects their browser to the Twitter authentication page. They’ve copy/pasted the URL they land on into a help request. The
oauth_token parameter is correct, i.e., it matches the token we stored on our end. Here’s an example from one of their attempts.
After entering their username and password, they are redirected to their Twitter homepage, rather than back to the application as expected.
With over 500K accounts created successfully, 70 in the past 24 hours, this is the only user I’m aware of encountering this issue.
The user was apparently successful in the past because the application was listed in their Twitter settings. But they must have deleted their account in our application because we have no access tokens stored for them.
They revoked the old tokens and re-tried with the same result: a redirect to their Twitter homepage. And, of course, the application no longer appears in their Twitter settings because without redirection back to the application, we’re unable to complete the 3-way authentication.
Any idea how we can track down the problem and resolve it?