iOS 12 users not yet out of the woods (straightdope)

[bordelond]

Long story short:

Up until the afternoon of Wednesday, May 11, the Discourse forum https:// boards.straightdope. com worked perfectly on my phone. That afternoon, the message board started only displaying a featureless white screen. The condition persists today.

I am using an iPhone 6 that was then running iOS 12.5.4 (now 12.5.5 which is as far as iPhone 6s can go). I have tried the latest Safari version allowable with 12.5.5, and have tried the latest Chrome version I can install (v. 92.0.4515.90 – needs to be at least v. 100 if my research has been accurate). Have not yet tried Firefox or Opera.

In Safari, I CAN view many of the forum contents with Javascript disabled, but so many forum features are disabled that site navigation is difficult. This is a diversionary for-fun message board, so the level of effort sans Javascript isn’t worth it.

Have already read through to the end of the threads below. If I’m following correctly … after the latest Discourse update(s), Discourse forums ARE, indeed, supposed to work on phones running iOS 12.5.5? Or sometimes yes, sometimes no?

Anything further that I should be considering, adjusting, fixing, etc? I am not a software developer or anything, but I am comfortable going through Safari’s Experimental Webkit Features in the iOS Settings – in fact, I’ve tried several of them, but haven’t hit on anything that worked.

Blank page when using iPhone 6 since last 16th March

Just would like to let everyone know that I have the same issue. I have an iPhone 6S running iOS 12.2, which btw I don’t plan on replacing or updating. I am an active user at https://support.last.fm/ but since a few days ago I just get a blank page on my phone, whatever browser I use. I have the Discourse Hub app which stopped working. Recently, I’m only shown the “browser is too old” banner" as shown below: [IMG_2094] Will this issue be fixed for iOS <13 users? I don’t want to buy a new ph…

Discourse not loading on legacy browsers

For iOS < 13 or deprecated Firefox Fennec on Android, we should be showing the HTML view. However, we are failing to do that because there is no HTML view due to which is in our code base since forever. Including the crawler content so we can fallback to HTML view is expensive, so maybe we want to add old Safari to so it’s done only when necessary? The other alternative being telling Babel to transpile replaceAll / finding a good enough polyfill. cc @sam @david @gerhard

Thanks in advance for any advice or assistance anyone may offer.

[david (David Taylor)]

We had an iOS12 issue last week which has now been fixed. The fix hadn’t yet been rolled out to straightdope. I’ve just expedited that, so it should start working again now. If it’s still broken, please do let us know.

Note that we will be dropping support for iOS 12 in January:

Maintaining support for iOS 12 - 14 until January 2023

Our policy has always been to support the “latest, stable releases of all major browsers and platforms”. However, given the large number of still-in-use Apple Devices which are limited to iOS 12, we have made a temporary exception: We will aim to support Safari on iOS 12.5 and iOS 13 until January 2023. Discourse 3.0 will be the last stable version to ship with iOS 12 / 13 support. After Discourse 3.0 is released, iOS 12/13 support will be removed from tests-passed (the default version used by …

[bordelond]

Thanks for the feedback, @david . Many small aggravations with the ol’ iPhone 6 have been cropping up over the past year or so … so the impending sunset of Discourse support will be one more nudge towards getting a “new to me” phone.

( @codinghorror , I thought you were primarily a member over at the SDMB – didn’t realize you were over here, as well )

[bordelond]

… and we’re back! Thanks for the quick response, @david !