twitter-api-client icon indicating copy to clipboard operation
twitter-api-client copied to clipboard

"LoginFlow is currently not accessible" when loggin using username

Open zekhoi opened this issue 1 year ago • 10 comments

I always fail when try to login, its because we dont generate x-client-transaction-id in the headers, any solution for it?

zekhoi avatar Aug 15 '24 01:08 zekhoi

I was actually gonna debug this issue as login started to fail to me as well... waiting for some responses

satinfive avatar Aug 15 '24 07:08 satinfive

i got a reference to generate it

zekhoi avatar Aug 16 '24 08:08 zekhoi

same issue here, trying to debug error, in my acse i gen random id for each login with random string, here is the spefific errror:

We blocked an attempt to access your account because we weren't sure it was really you.\n\nThis happens when we notice unusual login activity, like an attempt to log in too many times, or from a different location or device.\n\nYou'll need to wait before trying to log in again. Some blocks are removed automatically

image

Im looking how to gen id

hmchile avatar Aug 16 '24 12:08 hmchile

i got a reference to generate it

i think maybe not related, due to my message i think can be user-agent problem.

Here is conclusion of your reference:

Now what I wanted to do was make this into a simple localhost HTTP API to use it in a tool to check if using this header correctly would increase account quality when doing stuff on Twitter, like tweeting, liking posts, following people, etc. I'll spoil the result, it's completely useless. The header doesn't make Twitter "trust" your request any more or less. I guess it's just there to gather data right now, however, it makes me wonder; Why go through so much effort making this whole dynamic key system, obfuscating the files, etc. just to do practically nothing with it? At least nothing that would warrant obfuscation like that.

hmchile avatar Aug 16 '24 12:08 hmchile

I mentioned it's related to x-client-transaction-id because removing it from the browser request results in an error

Screenshot 2024-08-17 at 20 42 59

"I guess it's just there to gather data right now", the article written in Feb 2024. Maybe Twitter/X has since updated the purpose of this header? I'm not sure.

zekhoi avatar Aug 17 '24 12:08 zekhoi

What about this? tweeterpy/tid/transaction.py

JulienMaille avatar Sep 01 '24 16:09 JulienMaille

What about this? tweeterpy/tid/transaction.py

Have you tried it? It didn't work when I tried, same error

zekhoi avatar Sep 02 '24 05:09 zekhoi

What about this? tweeterpy/tid/transaction.py

Have you tried it? It didn't work when I tried, same error

No I haven't tried. What have you tested? The library or porting that bit of code?

JulienMaille avatar Sep 02 '24 08:09 JulienMaille

What about this? tweeterpy/tid/transaction.py

Have you tried it? It didn't work when I tried, same error

No I haven't tried. What have you tested? The library or porting that bit of code?

It actually works with their library, I just need to make a small adjustment in my code maybe (customize twitter-api-client)

zekhoi avatar Sep 02 '24 09:09 zekhoi

Hi, have you found a solution?

SzymonJot avatar Sep 24 '24 18:09 SzymonJot