Yep, it’s really annoying.
However, the reproducibility is not 100%. After a few tries, it worked for me and I’m now logged in for the foreseeable future.
But I can’t find a reliable way to bypass this f*** warning
To bypass Google’s check, open about:config in the default browser and search for “agent”. Change Sailfish 3 with Android 8 in the user agent string. This lasts until restarting the browser.
Weird, even this is set in the prefs.js file when modifying it via about:config, it gets overriden with the default on restarting the browser. Even killing all affected processes does not help.
wiered, a few weeks ago it worked fine for me, read this thread, tried it, failed. however, i do not use Gmail etc that often, on this page my keyboard hides what i m writing, thats also pretty annoying. but i can confirm your problem.
Thanks, it saved me. For whoever tries this, the string to replace is “Sailfish 3.0” with “Android 8.0”, be precise because befor I had used “Android 8” and it didn’t work
Tried in a private windows and was able to log-in at first try, so it seems so!
Haha, it actually works for me EDIT: Argl, the time to write this answer and BIM, phone rebooted, the good old browser RAM leaking until the OS can’t breath anymore I guess indeed
So maybe a new bug then (worth to be filled as?) As on my SFOS3.2 with older browser onky the browser crashes. But having the whole phone shut down abrupt is not a good thing!
Yes, that was yesterday.
And even today I managed to do so.
But not with stored/cookied user (where I received error about java script). I needed to click different account, gave my user and password and was in.
STRANGE is that I cannot enter from other phone or computer where it says password incorrect.
Funny as I enter same pass on both phones exactly same…
?