Users of the Firefox browser for Android have been reporting that they are seeing a blank page when trying to load the main Google Search site.

The issue:

Android users with Firefox can’t access Google Search (including intl sites and localized domains like google.de, .co.uk, .com.br). Instead, they see a blank page.

Cause:

A server-side bug on Google’s end related to User-Agent (UA) sniffing, which serves an empty page to newer Firefox versions.

Affected versions:

All Firefox versions on Android (>= 65) including Mobile 121.0, Nightly 123, and older.

Chrome not affected:

The bug is specific to Firefox.

Solutions:

  • Use a different browser (Chrome, etc.) or search engine (DuckDuckGo).

Advanced users can:

  • Change Firefox’s UA in developer settings or with add-ons.

  • Request the desktop version of Google from Firefox settings (region-dependent).

Status:

  • Problem identified as critical and escalated.
  • Still unresolved at the time of reporting.

Additional notes:

  • Disabling Firefox’s Enhanced Tracking Protection doesn’t fix the issue.
  • Some users report google.co.in loading the desktop site instead of mobile.
  • Katlah@lemmy.dbzer0.comEnglish
    1271·
    11 months ago

    “bug” aka purposely making firefox unusable on one of the largest websites in the world so more people use chromium

    (these allegations are based solely on prejudice against google and its subsidiaries, and do not necessarily hold true in reality)

    • KptnAutismus@lemmy.world
      25·
      11 months ago

      perfectly reasonable and logical prejudice, i might add. we really need to get people to use alternative search engines. google has been sucking fat balls for a long time now. either people are going to start to switch, or the frog will continue boiling.

    • Cyborganism@lemmy.ca
      13·
      11 months ago

      Even if it’s for only a short period of time, it’s enough to do a lot of damage. Especially as people are becoming privacy conscious and are looking to start using Firefox.

  • nieceandtows@programming.dev
    22·
    11 months ago

    I tried signing into Google today on Firefox and got ‘sigin in using a safe browser. This is not a safe browser’. I refreshed the page and it was gone and I was able to sign in. What the heck.

  • JK_Flip_Flop@lemmy.world
    22·
    11 months ago

    After intending to for years, I’ve recently switched to DuckDuckGo after getting increasingly frustrated with Google’s search results. This makes that decision feel all the more like the right one.

    I find it hard to say this is deliberate on Google’s part but at best it’s yet another case of Google blatantly skipping over Firefox testing.

    • Carighan Maconar@lemmy.world
      101·
      11 months ago

      I did so, too.

      I’ve done so repeatedly over the past years, each time giving it one month to evaluate how useful its result are to my productivity before deciding whether to swap back.

      After now giving it three months, I can say this:

      • As much as I complain about Google’s results having gotten worse, fucking hell is Bing sad (which AFAIK is still the majority of DDG’s result input). It’s orders of magnitude less useful than what Google digs up for my mix of gaming, board gaming, cooking, trivia knowledge and programming input.
      • Apple Maps is still an insult to people actually wanting to find things on a map on a desktop system and I cannot believe they have not replaced it with something else, no matter what. Openstreetmap would be a godsend. The current state just means I used an extension that hardwired Google Maps into it so I don’t have to add the !-command each and every time.

      In theory though, DDG is nice. If they can improve the quality of their results, I can work around the maps issue. But it’s still significantly behind Google, but I also have to see this in context of course: Google has a fuckton of money to throw around, for the budget they have, DDG is impressive.

  • skizzles
    14·
    11 months ago

    I’m on 121.0 mobile and have no issues accessing Google.com. Not that I use it anyway but figured I’d test.

    • beta_tester
      3·
      11 months ago

      Looks like it’s over. I could confirm the bug yesterday as well

      • skizzles
        2·
        11 months ago

        Weird, I suppose it makes sense though as I only really use Google if I absolutely have to which is almost never. So I likely wouldn’t have noticed it if I didn’t see it here first.

  • JokeDeity@lemm.ee
    12·
    11 months ago

    I really don’t understand why Google isn’t being taken to court over the obvious monopolistic strategies they’ve been implementing.

    • PoliticalAgitator@lemmy.world
      151·
      11 months ago

      And it was never broken for Chrome.

      Google can do plenty of damage to Firefox in a few hours and the best way to do it is to simply not include Firefox in their testing. If you don’t know the standards the web is built on, it makes FF look unreliable, despite it being Google’s bug.

  • 1984@lemmy.today
    7·
    11 months ago

    Real professional engineers at Google. Reading the browser name is just so hard.

  • Aurix@lemmy.world
    41·
    11 months ago

    It works here with the latest version. But moved to Kagi recently and very happy with the search results.

  • Carighan Maconar@lemmy.world
    3·
    11 months ago

    Interesting, from Germany the Google homepage loads normally but shows the old version (while the search results page uses the new version). Either they partially fixed it, or Firefox in its beta version already works around the problem in some way.

  • albert180@feddit.de
    2·
    11 months ago

    Yeah they have so many “convenient” bugs discriminating Firefox that there is already for a few Years a special Add-On that switches the User Agent to Google for the Search