Description
For a few weeks, I’ve been getting an error message quite often when I’m trying to log in from the gmail page, on a desktop PC using Brave on Windows 10.
After I enter my login ID (not my password yet), I get this message:
I’ve been using Brave for 9 months or so, and I never had this problem once before. Now, it happens about 30-40% of the time (I log on and off every day). I haven’t changed nor installed anything on my end.
Version
I’m using Brave version 1.79.118 x64, on Windows 10 22H2 x64.
Other information
Before, I was using Chrome. It’s still installed, so I did a series of about 10 login tests, but I couldn’t reproduce this error with Chrome.
I’ve searched a little and found similar reports, but nothing helpful or conclusive (or even recent), so I’m not sure whether it’s the browser or something else.
In a Brave Browser New Window, go to the Brave Browser (“BB”) settings page: brave://settings/content/siteDetails?site=https%3A%2F%2Fgoogle.com
Scroll down to JavaScript and either, set that to “Allow” or verify that the setting is already “Allow” ← maybe toggle that setting.
And repeat those steps for gmail.com → go to the Brave Browser (“BB”) settings page: brave://settings/content/siteDetails?site=https%3A%2F%2Fgmail.com
Next, go to: https://community.brave.com/t/brave-keeps-logging-me-out-of-google/599655/5 . . . and Add / edit the list of sources for Google eco-system JavaScripts.
I’m never logged out, though. I just often have to log in several times, especially for one specific account (sometimes, I even have to try several times before I can enter the password).
Sometimes, I have to disconnect, wait, reconnect . . . VPN service, and that resolves the issue.
Sometimes, I have to restart the computing device, then peck around YouTube, and finally it plays.
Sometimes, I use Vivaldi browser ← that works; and sometimes, after using Vivaldi, then BB works.
I suspect that Google is looking for enough “fingerprint” material, computing device “identifiers” . . . and then, “it works.”
Applying that to a Google account - that might help(?), but I do not have a Google account, and I have not been able to dig further - monitoring the sequence of network activity.
TIP: Use and compare the Developer Tools > Network windows of all of BB, Firefox, and Microsoft Edge.
Stealthily Google makes it harder for other competitive browsers to login, especially brave, because of its shield, ad blocking capabilities, it will not bother you if you use Edge, Chrome or Safari, the three musketeers. Google does everything it can to prevent users from using any other browser.
It’s not a network issue since I don’t have that in the same environment and Chrome.
It’s a problem in the Brave browser, which seems to fail something during the login that makes the server thinks it’s not JS-compatible. The identity is taken from a cookie, so I don’t have to enter my identity, just confirm I want to log in. It happens after that and before the server sends the password form.
This morning, I had to retry 3 times.
I suppose I’ll just report it as a bug; I thought it was worth asking here first. Since it’s a recurrent problem, I thought others who had it could give some hint.
Edge, Chrome, and Brave now use the same browser engine, as well as a series of others (and Safari is for macOS).
I suspected it might have something to do with the way Brave reacted to the Manifest V3 extension, but it sounds a little too conspiracy-theory. A non-compliance issue from either side seems the most likely explanation to me. Maybe Google has changed the protocol and is testing it in a region.
I also noticed it didn’t happen on my first account—I have to mention I’m logging in into two email accounts (sometimes more). The sequence is a little different than the first account, for some strange reason:
when I click on “Sign in” (when the identities are already in cookies), it goes straight to the password form for the 1st login
When I click on “Sign in” for the next login(s), it goes to an intermediate, useless page just to mention it needs to verify the identity. There, I have to click “Next” to get the password form, and that’s where it fails quite often.
EDIT: Scratch that, it happens on the first login, too.
