Open Adzetko opened 1 year ago
hensm
commented
1 year ago Seems like Twitch doesn't like the user agent spoofing. You could try some different user agent string variations. Might also be an issue with the way user agent headers are handled for requests with a whitelisted origin since it seemed a little broken in the testing I did.
Adzetko
commented
1 year ago Sorry I only see your answer now, I don't have any user agent string setup so I don't really think the problem comes from that? I mean, I suppose it keeps the default Firefox string if I don't input any string?
Zachruff
commented
1 year ago I had the same issue, also wouldnt let me do a Prime Subscription to a streamer.
Bareno
commented
1 year ago There seems to be some issue with fx_cast causing integrity check issues, it completely breaks twitch for me when I have fx_cast enabled, for example the following errors happen when I attempt to create a clip while watching a stream. Instead of creating a clip, a blank tab appears and it spurts out these errors.
OS version: Windows 11 21H2 Browser version: Firefox 109.0 (64-bit) Extension version: 0.3.1 Bridge version: 0.3.0
`[GraphQL] One or more GraphQL errors were detected on request 01GS1K0V8SJS0R9BPVCJT4AXKN. createClip: failed integrity check Array [ {…} ] 0: Object { request: {…}, response: {…} } length: 1
hensm
commented
1 year ago I guess I misread the original post. I can't reproduce the behaviour unless Twitch is whitelisted (rather than simply having the extension enabled), so it would be good to get some confirmation on that specifically. I still think it's likely to be related to other resources on the page being loaded with a different user agent string. I'll see if I can track this down tomorrow.
hensm
commented
1 year ago Using a Chrome user agent string globally also causes these issues, so it's probably Twitch doing some sort of hacky browser detection for bot prevention or something which I'm not going to try to figure out. If anyone has a solution, I'll accept a PR. Otherwise, Twitch is unsupported.
As far as Twitch breaking just from having the extension enabled, I need either steps to reliably reproduce this on a fresh Firefox profile or some useful info that would help me track this down.
OS version: Windows 11 22H2 Browser version: Firefox 107.0 (64 bits) Extension version: 0.3.1 Bridge version: 0.3.0
Description I logout to my Twitch account while the extension was active on Firefox (and https://www.twitch.tv/* was whitelisted). When I tried to login back, the POST request to https://passport.twitch.tv/integrity sends back an error 400 (as seen in the networking tab of the firefox dev tools), the Twitch's JSON response stated "error_code":5025 and "error_description":"integrity failed".
Disabling the whitelisting for Twitch in the extension's options didn't work, I had to fully disable the extension to be able
Steps to reproduce
Expected behaviour The extension should not prevent users to login to their twitch accounts
Logs I'm not really sure I could provide logs of the request without leaking my twitch password, sorry!