This topic was automatically generated from Slack. You can find the original thread here.
Having difficulty with connecting to my Twitter account. I’ve followed all the directions to get my consumer API Key and Secret. I’ve configured the callback URL, etc. When I enter the consumer key and secret into Pipedream and click Connect, I am taken to the Twitter login page (2fa is disabled). so far so good… When I log in, I’m simply taken to my timeline and nothing else happens. Here’s the URL I see after I clicked Connect in Pipedream:
Hi , this is a known issue on the Twitter side - the OAuth flow is broken for some users and we’re tracking the issue in this ticket in the X Community - their team has said that they’re looking into it, but we have not gotten any timelines as to when this would be fixed.
I know the thread mentions “for accounts with 2FA”, but as you’re reporting and other users have as well, this appears to be impacting accounts without 2FA as well. Something is broken with their redirection process in the flow.
Sporadically broken. I can’t reproduce the error, but some users hit it, others don’t and there’s no guidance from their team yet, but they’ve confirmed the issue.
The only other troubleshooting step that I could think of would be to clear your cookies/cache, log out of X, try to connect again on Pipedream. I’m watching the thread with X and as soon as I hear of a fix, I can follow back up here. Sorry for the issue - understandably not ideal but it has been difficult getting any timelines from the X Developer team.
I made the call to temporarily hide the Twitter app, as we’re seeing a low percentage of users actually being able to connect to Twitter due to the bug you described. I intend to re-enable this once we have Twitter engaged to fix the OAuth redirection bug on their side.