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

Please add ability to deal with geetest during daily check-in #118

Open
jokelbaf opened this issue Aug 16, 2023 · 1 comment
Open

Please add ability to deal with geetest during daily check-in #118

jokelbaf opened this issue Aug 16, 2023 · 1 comment

Comments

@jokelbaf
Copy link

There is a chance of triggering geetest (captcha) during daily check-in. Although the retcode is 0 and message is 'ok', gt_result object is returned by the API. It is pretty obvious that the library can't solve captcha but it will be really cool if geetest data was returned by genshin.daily.claim() and there was a way to retry this method with solved (manually) geetest.

Here is an example response of the request sent to DAILY_CLAIM_API (Genshin) endpoint when geetest was triggered:

{
  data: {
    code: 'ok',
    first_bind: false,
    gt_result: {
      risk_code: 5001,
      gt: 'a280f1e34s45a37ae91c65fc745fba71c',
      challenge: 'ef74ab0042086a343ba869f5e29dab6e',
      success: 1,
      is_risk: true
    }
  },
  message: 'OK',
  retcode: 0
}

Note: Looks like success in gt_result is 0 if API accepted solved geetest.

@jokelbaf
Copy link
Author

When retrying request with solved geetest it must be put in headers:

image

An example of response after successful request to daily endpoint with solved geetest:

{
    "retcode": 0,
    "message": "OK",
    "data": {
        "code": "ok",
        "first_bind": false,
        "gt_result": {
            "risk_code": 0,
            "gt": "",
            "challenge": "",
            "success": 0,
            "is_risk": false
        }
    }
}

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

1 participant