Closed Bug 1915442 Opened 2 years ago Closed 1 year ago

Search engine defaults to Bing despite another engine being set as default

Categories

(Firefox for Android :: Search, defect, P2)

Firefox 129
All
Android
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: amoya, Assigned: skhan)

References

Details

(Whiteboard: [fxdroid][group3][s2-2025])

Steps to reproduce

Reported through Google Reviews: “What the hell is that game that Firefox playing with us and changing by itself to search on Bing? Right now it's the end. I'm moving to another browser. Firefox suppose to be the best by they sold us to the devil. Shame”
Another report here: https://play.google.com/console/u/0/developers/7083182635971239206/app/4972519468758466290/user-feedback/review-details?reviewId=1d386f39-17aa-45a5-9de7-3b32ff979e87&corpus=PUBLIC_REVIEWS
1.
2.

Expected behavior

Firefox should honor default Search engine choice of user.

Actual behavior

Bing search results are returned.

Device information

  • Firefox version: v129
  • Android device model: Various devices (Samsung S21, Huawei, Xiaomi)
  • Android OS version: Android 10, 13 and 14

Any additional information?

The severity field is not set for this bug.
:skhan, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(skhan)
Assignee: nobody → skhan
Severity: -- → S2
Flags: needinfo?(skhan)

Some things to start the investigation:
There are reviews that state the previous version they were using started the issue (v127).

This could be caused by a swiftkey keyboard causing default search to jump to Bing based on this report:
https://support.google.com/websearch/thread/291626003/chrome-search-redirects-to-bing-android-phone?hl=en

Note: This sounds like it's occurring in Chrome as well.

Priority: -- → P2
Whiteboard: [fxdroid][group3][s2-2025]

Note from Petru, Swiftkey Keyboard chat feature may have changed and removed this issue. It now requests a Copilot installation. Investigating the root cause of this may require finding an older Swiftkey version.

Closing this as "WONTFIX" based on Zac's comment here.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.