Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"LoginFlow is currently not accessible" when loggin using username #228

Open
zekhoi opened this issue Aug 15, 2024 · 10 comments
Open

"LoginFlow is currently not accessible" when loggin using username #228

zekhoi opened this issue Aug 15, 2024 · 10 comments

Comments

@zekhoi
Copy link

zekhoi commented Aug 15, 2024

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

@satinfive
Copy link

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

@zekhoi
Copy link
Author

zekhoi commented Aug 16, 2024

i got a reference to generate it

@qwerty724
Copy link

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

@qwerty724
Copy link

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.

@zekhoi
Copy link
Author

zekhoi commented Aug 17, 2024

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.

@JulienMaille
Copy link

JulienMaille commented Sep 1, 2024

What about this?
tweeterpy/tid/transaction.py

@zekhoi
Copy link
Author

zekhoi commented Sep 2, 2024

What about this? tweeterpy/tid/transaction.py

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

@JulienMaille
Copy link

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?

@zekhoi
Copy link
Author

zekhoi commented Sep 2, 2024

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)

@Szymjotek
Copy link

Hi, have you found a solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants