-
Notifications
You must be signed in to change notification settings - Fork 57
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
Not working for Genshin #16
Comments
Same here. Started about 3 days ago. Discord push message says "sign OK" but actually it did not sign. If I try to sign in manually with hoyolab, an image verification pops up. |
I think that it might be some kind of anti-bot thing because when I use an alt to sign in manually there is no verification. |
I guess so. In this case the bot should return an error message to indicate the failure of signing in. However, it send an "OK" message to the discord server. This should be fixed I believe. |
Might be a bit hard to fix the "OK" message, as this is what HoYoLAB is returning from the API request. HoYoLAB is telling us that the check-in worked when it didn't. |
Can we maybe add user-agent, and x-http-referrer reader to the scripts and. The end-server are probably checking for user agents and referrer like mentioned here: #11 (comment) My account started to require captchas this day after succesfully checking in with the script for 12 days I will try to add the code to the const header = {
Cookie: token,
'x-rpc-app_version': '2.34.1',
'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36',
'x-rpc-client_type': '4',
'Referer': 'https://webstatic.mihoyo.com/',
'Origin': 'https://webstatic.mihoyo.com'
}; |
this change to header worked for me |
My account still requires captcha even after putting those header in the script. The verification process probably done randomly or after certain days passed after checking-in without a user-agent/referrer, just a speculation though, cannot confirm anything... Probably we want to push in the header changes to main anyway, just to make the script more like a human action to hoyoverse server logs. |
yeah i agree, do u wanna do the pull request? i dont wanna take credit for ur work lmao |
I've opened one at #17 please have a look |
Today, the script successfully checked in my genshin account without captcha verification. Will report here again if the captcha came back. |
This is an example of API response. I am temporarily using |
A commit in a similar python project seems to include some challenge parameters in the header: |
seems to be working once again by doing nothing. although the captcha in the browser still showed up when you claim check in manually |
It´s broken for me again :( (Telegramm) After I manually collected it, it´s giving me the same message. |
Not working for me today, and using updated HTTP Headers from the Pull request #17 . I just started using this a few days ago so I have never ran the code without the HTTP headers. HSR is functional, Genshin is encountering the CAPTCHA even after manually collecting. Edit: Update on Functionality. I don't fully understand tokens/http headers, but it seems like if the exact same HTTP check in request 2 days in a row (perhaps also same time of day) occurs, then the CAPTCHA is triggered for Checkin. |
Mine also started breaking today. I can see some repo (like one mentioned above) might able to successfully bypass the geetest captcha, but i would not want to do it. Pretty sure it's borderline against their ToS. Will report here again if i find another solution. |
The entire script already is. |
I needed to change
|
The script seems to be no longer working for Genshin (Still works for Honkai and Star Rail).
The text was updated successfully, but these errors were encountered: