Closed codilau closed 5 months ago
are you calling asyncAuthenticate first? this function does not require any arguments
On Sun, Apr 28, 2024 at 11:47, codilau @.***(mailto:On Sun, Apr 28, 2024 at 11:47, codilau < wrote:
Hi, thanks for this great tool. It looks very promising. I was interested in the account.unlockViaArkoseCaptcha() function but can't make it work and I;m not sure where I'm screwing it up. Would you mind sharing a usage example? I've got a API key for twocaptcha
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
also make sure you add debug=True to the init
as well the twocaptcha key is provided at init and not when the function is called
today i will add some documentation to init and unlock and authenticate and give real var names and type hints instead of args kwargs
I'm instantianting as in your example passing the twocaptchaapikey as kwarg then I'm calling asyncAuthenticate, passing cookies as kwargs. Then I tried a few things around await twitter.unlockvia... with no arguments
the example provided in testAsyncTwitter.py is what works for me on many accounts, so if its not working for you i have no idea why sir i apologize, note that sometimes twocaptcha provides invalid captchas or provides no captcha at all and can take 3+ tries for a single unlock
if you wish to debug yourself use vscode python extension and clone the repo into the same dir youre workign in and add breakpoints on the responses and manually check them yourself. pushing an update shortly with some docs + type hints for ides
Another issue might be that it submits lang: en, if account isnt english maybe a problem
I just pushed an update that upgrades a lot, try now
Also realized was a problem with the debug logger i fixed
Fixed another issue with the unlocker, wasnt working in last update should work now
Going to consider the issue closed perhaps unless more information is provided, refer to testAsyncTwitter.py
hmm seems there is still something wrong with the headers after a bunch of updates, gonna look into it more when i can
I think i finally found the issue, i think it was related to it accidentally sending the wrong cookies due to it having a cookie header from copying the headers and having cookies from copying cookies, also decided to add more headers that chrome was sending with the request.
I think it should properly support accoutns with other languages now as well, cleared a lock on a pt and a en account.
Please let me know if there is still an issue, will close in a few days if no reply
There is a ui_metrics that gets sent in the POST body, currently its static as I have no idea how to generate it, would be much appreciated if someone figures that out
More updates added, it's very reliable now I find
Brilliant mate! Awesome work and thanks a lot for the effort. It now works as expected. I'll keep using and exposing other bugs I might find!
There are quite a few things needed to be done, there are various discrepancies in asyncAccount & scraper & search because Trevor decided to have them use a different login() for each file, unifiying these functions into one location and unifiying the logger functions would be something important to do
Also missing tons of documentation, has awful variable names in some places as well.
Theres also some other stuff in the TODO in README.md, considering forking and contributing<3 Also consider sponsoring project or trying to advertise it in anyway as I'd love for people to know this exists
Hi, thanks for this great tool. It looks very promising. I was interested in the account.unlockViaArkoseCaptcha() function but can't make it work and I;m not sure where I'm screwing it up. Would you mind sharing a usage example? I've got a API key for twocaptcha