1668842 - [Bug] Can't load any webpage because of XML parsing error

Status: RESOLVED INCOMPLETE

(GeckoView :: General, defect, P2)

Description

[Kevin Brosnan [Ex-Mozilla]]

From github: https://github.com/mozilla-mobile/fenix/issues/14700.

Steps to reproduce

1. Go to any website

Expected behavior

Loads website

Actual behavior

Shows a blank screen. If you click on the URL, there will be a brief moment where you can see the error message

XML Parsing Error: no root element
Location: chrome://geckoview/content/geckoview.xhtml
Line Number 1, Column 1:

^

Device information

• Android device: SM-J737V
• Fenix version: 80.1.2 (Build #2015761281)

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

There are a few comments in the Github issue. User's device is set to English and Fenix is set to use device language. There is another user that has run into this problem as well.

Comment 2

[Kevin Becker]

I have the same bug. Funnily enough I had to download FireFox Beta to continue using Firefox as it is an older version and still works.

Not a single website loads and it shows the above error message in the tiny website preview.

Android: 10 - LineageOS 17.1-20201217-NIGHTLY-bacon
Device: OnePlus One

Updated Firefox to
84.1.1 (Build #2015781793)
AC: 67.0.12, 24dd57cfd
GV: 84.0-20201211215739
AS: 67.0.0
today. Since then getting the error.

I'll try to attach an image.

Also, this bug prevents other apps from using Firefox as a built-in browser.

Comment 3

[Kevin Becker]

Attachment: Preview window shows error while page stays blank.

Comment 4

[Kevin Becker]

I just updated to
84.1.2 (Build #2015783145)
AC: 67.0.14, 8b9aabdda
GV: 84.0.2-20201223151259
AS: 67.0.0
and the issue is resolved for me.

Comment 5

[chrisdeloughery]

I just updated to 84.1.2
AC 67.0.14 8b9aabdda
GV: 84.0.2-20201223151259
AS: 67.0.0

And this issue just started presenting itself. Nightly is working.

Comment 6

[Kevin Brosnan [Ex-Mozilla]]

https://github.com/mozilla-mobile/fenix/issues/20390

Comment 7

[Chris Gregory]

I was reproducing this issue after updating Firefox. Reinstalled and it works again

Comment 8

[Seburo]

User reporting this issue in SUMO: https://support.mozilla.org/en-US/questions/1348009

Comment 9

[smow]

I'm facing this issue after updating to Nightly 101.0a1 (Build #2015873355)

4c25257c5+
AC: 101.0.20220407143154, e5965fb99c
GV: 101.0a1-20220407092959
AS: 91.1.1

Force closing app and clearing cache doesn't seem to resolve it.

Device: Xiaomi Mi 10 Lite 5G

Comment 10

[smow]

(In reply to smow from comment #9)

I'm facing this issue after updating to Nightly 101.0a1 (Build #2015873355)

Surprisingly, after an hour everything seems to work fine. 🤔

Comment 11

[Daniel Holbert [:dholbert]]

Are we aware of anyone still reproducing this? Comment 7 and comment 10 indicate that it went away.

(I see other users reported it happening after an update but potentially disappearing after clearing cache or storage. That's not a great workaround to offer, so to the extent that folks still hit this, it would be great to fix. But I wonder if any users are actually still/newly running into this at this point.)

Comment 12

[Kevin Brosnan [Ex-Mozilla]]

Checked with support and they have not seen any instances of this. Opening a new bug is cheap and may have better context.