Closed
Bug 767262
Opened 12 years ago
Closed 3 years ago
google search returns a 502 error
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: fiotakis, Unassigned)
Details
Attachments
(1 file)
104.60 KB,
image/png
|
Details |
Trying to search for any term via the address bar (or by taping on "search google for -search term-", returns a 502 error page from google. If I navigate to google and then perform a search from the page, it works fine. I'm using the latest aurora (native) build 15.0a2 on a samsung tablet with android 4.0.3 (el locale).
Comment 1•12 years ago
|
||
WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #1) > WFM. Since i have not installed any addons on Aurora, do you have any hints on what might cause the problem? Please note that I also have installed the stable and nightly versions and at least on the stable it works fine (can't remember about the nightly and I wont be able to check it 'till tomorrow). My guess now is that something is configured in a wrong way in google's locale settings for the device's version of android, should I file a bug on their side and provide a link to this one?
Comment 3•12 years ago
|
||
Hey George, Did you happen to have Phony installed and set as the iPhone user-agent or another particular user-agent from within Phony?
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
Reporter | ||
Comment 4•12 years ago
|
||
As I said, I had no addons installed. I did installed Phony now and though it didn't work at first (user agent setting to "default"), after I switched to "desktop firefox" it does work (even when i switch back to "default".
Comment 5•12 years ago
|
||
I have 14 votes for this problem on SUMO this week, see https://support.mozilla.org/en-US/questions/929665 I experienced this yesterday on my HTC EVO shift with Phony, but didn't have a logger hooked up, though it is captured in my history, see attached screenshot.
Comment 6•12 years ago
|
||
Comment 7•12 years ago
|
||
I've only seen this when searching from the AwesomeBar with Phony installed and set a different user-agent such as Phony. It would be good to know if people are seeing this without Phony installed.
Reporter | ||
Comment 8•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #7) > It would be good to know if people are seeing this without Phony installed. Aaron, read again comments 2 & 4. In case my english are that bad, I had no addons installed at all when I submitted the bug report. Perhaps it would be also interesting to know if the users who are affected are using a localized android system.
Comment 9•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #7) > I've only seen this when searching from the AwesomeBar with Phony installed > and set a different user-agent such as Phony. > > It would be good to know if people are seeing this without Phony installed. I experienced the same error with addon Phony installed when searching via the address bar. After uninstalling Phony searching was ok. Firefox 14.0 Android 4.0.3 device Galaxy Nexus
Comment 10•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 3 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•