Blank Page on Android

papernoise · 2018-08-14T13:53:06.606Z

Since recently, accessing lines from my Android device (Fairphone with FPOpen OS) will just show a blank page. I tried both the stock browser and the DuckDuckGo one, but the result is the same.
Is anybody else seeing this?

tehn · 2018-08-14T14:07:38.414Z

have you experienced this with other discourse forums? (MI etc)

edit: try now that i enabled sitewide HTTPS

papernoise · 2018-08-14T15:02:24.058Z

I have checked and I get this with the MI forum as well, but not with other Discourse installs like community.blokas.io

tehn:

edit: try now that i enabled sitewide HTTPS

Doesn’t seem to have changed anything.

I’ve also emptied the cache and deleted the cookies, but to no avail.

tehn · 2018-08-14T15:18:52.289Z

we’re up to date with the discourse system, so perhaps it’s a bug introduced with a recent update (and blokas is behind?)

sandy · 2018-08-14T15:45:20.834Z

No problems here.
Chrome, Android 6.01, Nexus 5

steveoath · 2018-08-14T19:53:16.128Z

Don’t have fair phone, but running Android here. No issues using Brave browser.

b_w · 2018-08-14T20:19:46.633Z

I’m having this same issue. running chrome on a OnePlus 5. no dice…

dailybells · 2018-08-15T08:36:27.502Z

Possibly related? I get this from time to time when loading the site in firefox 61.0.2 on linux:

cce703×774 20.8 KB

A shift-refresh loads the site as normal.

Starthief · 2018-08-15T12:07:12.359Z

Works fine in Chrome and Ghostery on my Galaxy S7 with Android 8.0.0.

tehn · 2018-08-15T13:02:01.906Z

this might be related to the recent change of site settings to https. did you get the error repeatedly?

dailybells · 2018-08-15T14:32:04.403Z

It happens every few days, I can’t remember when it started! A few months ago? (IMHO not worth spending time on! It’s easy to workaround. Just wanted to add a data point.)

sakul · 2018-08-15T14:52:41.161Z

just a quick thought: any add-ons active doing their magic? also, tried clearing the cookies? (same to the op)

dailybells · 2018-08-15T15:12:35.316Z

I’ll see if I can figure out how to reproduce consistently. Just happened again, I haven’t noticed it when visiting other discourse-powered forums yet… it really hasn’t bothered me at all but happy to try to debug.

Update: the problem I’m seeing definitely just happens when the site is loaded from cache. Forcing firefox to make a request to the server loads fine, but anytime it attempts to use the locally cached version, I see that corrupted content error.

dailybells · 2018-08-15T15:23:34.799Z

This seems like it might be the same issue – problems when restoring session content:

github.com/WaterfoxCo/Waterfox

(Mozilla 1437080) service workers: load after unload, or session restoration, may lead to 'Corrupted Content Error' or 'Cannot load app'

opened 06:33AM - 24 May 18 UTC

closed 02:43PM - 15 Jul 18 UTC

grahamperrin

## Steps 1. https://meta.discourse.org/t/-/78008/24?u=grahamperrin 2. open a… new tab 3. quit 4. start 5. restore the previous session 6. bring the Discourse tab to the front ## Expected 7. automated load of the content ## Actual result 7. no load; > # Corrupted Content Error > > The site at `https://meta.discourse.org/t/cannot-load-app-for-a-meta-topic/78008/24` has experienced a network protocol violation that cannot be repaired. > > The page you are trying to view cannot be shown because an error in the data transmission was detected. > > - Please contact the website owners to inform them of this problem. > > **Try Again** ## Workaround <kbd>Space</kbd> Alternative workarounds include <kbd>Control</kbd>-<kbd>L</kbd> then <kbd>Return</kbd> or <kbd>Enter</kbd>, however for many users, it will be preferable to simply accept the invitation: - _try again_. ---- <details> <summary> Notes </summary> If you see 'Cannot load app' in lieu of 'Corrupted Content Error', please state the build of Waterfox, from: - about:support Please refrain from contacting the owners of meta.discourse.org. For this issue, re: http://www.discourse.org/about#browser we may expect the current release of Waterfox to be not supported by Discourse. If you find an instance of Discourse that is not affected by this issue, please state both: - the URL; and - the version of Discourse. Version information can be shown with [Wappalyzer](https://addons.mozilla.org/addon/wappalyzer/) or [its bookmarklet](https://www.wappalyzer.com/download#bookmarklet). Thanks </details>

papernoise · 2018-08-23T17:20:50.230Z

Not sure if this is the issue. I am having this with Chrome-based browsers. Though I did check Firefox Focus (always on Android) and I have the same issues there as well.
Interestingly various Discourse forums work (Elektronauts, blokas.io) so maybe it really is a matter of which version one is running.
Interestingly also the official Discourse forum does not work, giving me the same blank page as lines.
I was looking at where to file a bug report to the discourse team… but I can’t seem to figure that our. I can’t find the “issues” tab on their github page.

dailybells · 2018-08-23T17:35:14.113Z

I’ve noticed this also on the scsynth.org discourse forum FWIW, if there’s a problem with the way discourse reloads the cached session via service workers, it might not be browser-specific either…

papernoise · 2018-12-19T13:04:27.060Z

I did re-test recently and there seems to have been an improvement.
Fennec (a Firefox fork) works!
DuckDuckGo (Chromium based, IIRC, but I might be wrong), which previously didn’t work, now works fine.
So maybe the problem has been solved by the recent discourse update?

dailybells · 2018-12-19T19:38:03.441Z

I also haven’t seen this in quite a while – earlier this year it would happen to me at least a couple times a day.