What happens if the user-agent is spoofed to something else like Edge/Google Chrome/Firefox? (While leaving shields up)
Also have you tried with shields down? This could help determine what it is they are detecting and blocking specifically (either the browser itself since Brave by default presents itself as Chrome usually, or the anti-fingerprinting itself which is alarming that they want it that bad, like my CC agency I had to deal with, Brave wasn’t supported until shields were entirely down).
I was able to login about a week ago with the shield set to standard. I didn’t see the error message either. I added the Twitch Adblock Rules and the Experimental Adblock Rules filter lists.
Update your browser I am pretty sure thats what it means when it says your browser is not compatible. At least whenever ive gone to the site and its said that after updating its always worked
You have the latest update? Then my next guess would be are you using the content lists? It could be the experimental features.
Clear the browser cache
Check your browser extensions (if any)
If that doesn’t work then its definitely your browser settings. Most likely it’s detecting that your blocking something and want you to NOT do it.
So a content list that is enabled that it doesn’t like, third party cookies being blocked, or data not being able to be saved to the device.
That’s the only things that would cause that message to show. Review your settings and I’m sure you will see something that’s not enabled that should be or something disabled that should be. It’s not a brave browser issue. In my opinion, it’s more of a twitch issue. The next option is to talk to twitch support and you will get told to “just use chrome or edge because those browser work the best” at handing over all your data regardless of your settings.
It makes no difference if your using a VPN or DNS. dated, it’s one of the other things I mentioned. You would be less likely to have a problem logging in when your NOT using a VPN but either way on twitch VPN is not the problem. DNS not the issue. Would be a totally different outcome and not that message. Its the browser setup usually because you’ve got the latest version.