#1

I periodically hear from users of my application that they cannot sign in with Twitter. In the most recent case, the user captured screenshots and shared some details about what they are seeing.

They’ve been unable to sign on even after clearing their browser cache and trying from an incognito window.

After entering their Twitter handle and password and clicking the Sign In button, they get a page that says “That page has expired or dose not exist. Please try logging in again.”

I had them copy/paste the URL from the browser address bar at that point. I’ve modified it a bit here to protect their ID.

https://twitter.com/account/login_verification?platform=web&user_id=<elided>&challenge_type=Totp&challenge_id=<elided>%252&redirect_after_login_verification=https%3A%2F%2Fapi.twitter.com%2Foauth%2Fauthenticate%3Foauth_token%<elided>

For this user, it occurs repeatedly. Other users over the past several months have reported the same issue. I’ve suggested they try an incognito/private window and clear their browser cache if that works. I haven’t heard back from them, so assume that worked though I can’t verify that.

I previously reported this same issue in the Business Developers forum. I’m posting this new occurrence here for better visibility.

Is this a known issue? What information can I provide to help diagnose this so it can be resolved?

-Marc

1 Like
#2

Thanks, @semifor. I’m asking a few coworkers about this issue, and I’ll get back to you shortly.

#3

I talked to a few coworkers and learned this is a known issue. This happens on the Oauth 1.0a flow when the user is asked to verify recent logins (e.g., if we see suspicious activity and we ask users to verify). This is an issue because people cannot go back to the app. But instead, they go back to Twitter. I surfaced this with the relevant team, and I’ll let you know when I hear further.

#4

I just talked to our account security team and got some further clarity here. We might have missed some redirect logic handling since account/login_verification is deprecated. The team is working on a fix that should be deployed shortly.

4 Likes
#5

Thanks, @jessicagarson! Fantastic news. This will make customers happy.

#6

I may have spoken a bit too soon here. I just sent you a DM to discuss this a bit further. Sorry for any confusion.

1 Like
#7

Any further news on this @jessicagarson? Is there anything I can do from my end to help?

#8

Hey Marc,
Would the problem go away if the user logs into twitter.com first, then authenticate against your app?
If so, we have had plenty of these reports as well.
Thanks
Samir

#9

Thanks, @semifor. I’m going to send you a DM on this one.

#10

Hi Samir. Next time a customer encounters this, I’ll ensure we verify they are signed in, first. Thanks!

2 Likes
#11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.