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

[Bug] Failed to claim drop reward! Error: API error: failed integrity check #236

Open
neohazuki opened this issue Oct 19, 2022 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@neohazuki
Copy link

[2022-10-19 10:17:50] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:50] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:50] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:51] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:51] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:51] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:51] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:52] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:52] [error] Failed to claim drop reward! Error: API error: failed integrity check
[2022-10-19 10:17:52] [error] Failed to claim drop reward! Error: API error: failed integrity check

when start the bot

@neohazuki neohazuki added the bug Something isn't working label Oct 19, 2022
@AndyShade
Copy link

Use Chrome addon for you taste to clame drops,no autoclame.

@JourneyOver
Copy link

IMO the actual claim parts of the bot should just be removed at this point (perm or temp until a fix can be put into place), just have it watch streams and send out notifications.

@AndyShade
Copy link

AndyShade commented Oct 20, 2022

IMO the actual claim parts of the bot should just be removed at this point (perm or temp until a fix can be put into place), just have it watch streams and send out notifications.

Do own fork and make what you want

@BulldozerPete
Copy link

How to fix this bug in a docker container?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants