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

GQL RESPONSE ERROR #7

Open
StevensUneven opened this issue May 25, 2023 · 5 comments
Open

GQL RESPONSE ERROR #7

StevensUneven opened this issue May 25, 2023 · 5 comments

Comments

@StevensUneven
Copy link

Keep getting the following error:

`

npm run build && node build/index.js

[email protected] build
rimraf ./build && tsc

Successfully Loaded Settings...

Displayless mode enabled
Discord Webhook enabled

Found a twitch-session... No need to login...

Getting all active Campaigns...
Removed World of Warcraft from the Priority List, because there is no ACTIVE campaign with such name.
Removed Diablo III from the Priority List, because there is no ACTIVE campaign with such name.
Removed Diablo IV from the Priority List, because there is no ACTIVE campaign with such name.
Removed Halo Infinite from the Priority List, because there is no ACTIVE campaign with such name.
Removed PUBG: BATTLEGROUNDS from the Priority List, because there is no ACTIVE campaign with such name.
Removed Apex Legends from the Priority List, because there is no ACTIVE campaign with such name.
Removed Sea of Thieves from the Priority List, because there is no ACTIVE campaign with such name.
Removed Rocket League from the Priority List, because there is no ACTIVE campaign with such name.

Selected a Game from your Priority List watch: Call of Duty: Modern Warfare II

Getting all available Drops...
GQL RESPONSE ERROR! DropCampaignDetails Request Failed... Retrying in 60 seconds... Try: 1/4
GQL RESPONSE ERROR! DropCampaignDetails Request Failed... Retrying in 60 seconds... Try: 2/4
GQL RESPONSE ERROR! DropCampaignDetails Request Failed... Retrying in 60 seconds... Try: 3/4
GQL RESPONSE ERROR! DropCampaignDetails Request Failed... Retrying in 60 seconds... Try: 4/4
Unhandled Rejection at: Promise {
'[{"message":"failed integrity check","path":["user","dropCampaign"]}]'
}
Unhandled Rejection Reason: [{"message":"failed integrity check","path":["user","dropCampaign"]}]
`

Then app closes

@AirHeadsbuirse
Copy link

Same issue, guessing this is also dead.

@delta-whiplash
Copy link

hello everyone I have this issue too GQL RESPONSE ERROR! DropCampaignDetails Request Failed... Retrying in 60 seconds... Try: 1/4

@PivaRos
Copy link

PivaRos commented Oct 14, 2023

same issue for me

@rka
Copy link

rka commented Nov 3, 2023

Same here, this is probably dead :(

@BlayeeR
Copy link

BlayeeR commented Dec 18, 2023

I think they might have added some anti bot security into Twitch GQL Api. I was playing around with stuff and it looks like integrity token that we get in the bot seems to be invalid when trying to fetch drop campaing info. When swapped with one from my browser it runs just fine.
Not sure why other GQL operations work just fine, but kinda makes sense that they want to protect the drops from the abuse.
In the cookies and XHR request we can see some kpsdk stuff, which looking at the web might be related to anti automation measurements from Kasada.

So I think the era of browser-free twitch drop bots might be over. I hope that someone can prove me wrong.

Easiest way to farm drops now is to switch to other headless browser based bots that you can find easily on github. Also note that Twitch staff probably see all the requests with invalid integrity checks and that means they can easily determine if user is trying to setup a bot. Take care with your accounts!

Edit:
its the same issue as there: streamlink/streamlink#5370 (comment)
If we decode base64 the jwt token generated in the integrity endpoint, there is is_bad_bot property which is set to true for the token generated with this bot

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

6 participants