The first time I went to the SDMB on my iPhone today, there was a message on screen informing me that my browser (Safari) was not compatible.
A link directed me to browsehappy.com, where I could find more about other browsers.
But before I change browsers, I thought I’d see if anyone else has encountered this problem, and/or knows why it suddenly came up.
TIA.
I use Edge on my phone and iPad, no issues here
Posting this from my iPhone in Safari. No problems. iOS 16.2
You’re soaking in it. Used my iPhone with safari all day today, no prõblemo.
That’s a weird message to get - generally if an iPhone has an issue, it’s directing you to something inhouse. I’d even worry (slightly) about some malware in your browser cache so I’d recommend you follow the Apple steps below.
FAIR WARNING, this will normally delete all your saved passwords and settings for various websites, so you may want to make sure you have that backed up first.
The only other thing I can think of off the top of my head, is that if you’re using a (much) older iPhone model (first gen SE, iPhone 7 or earlier) it is no longer supported as of the current iOS 16. So if you have an old model, that MIGHT (still doubt it) be the issue.
This is off the top of my head as a (several years removed) former T-Mobile Tech support guy for phones.
I do have an old phone. I will ask my IT staff (i.e., my niece and nephew in law) this weekend.
Thanks!
No problem, while it’s not my job anymore, I’m always happy to help. Do keep the Apple tech flow I linked though, because I’d do that before setting up a new browser - you’ll lose stored info ANYWAY and if there is some malware in the browser, best get it gone.
But I’m sure your family will agree as well. Best of luck!
@F.U.Shakespeare , what version of the iOS is your phone running? Discourse was set to stop supporting some older versions of iOS this month. Start at about post #30 in the thread below and read through for more details.
Here’s the Discourse announcement for end-of-life for Safari on iOS 12 and 13:
Here is the specific text of the announcement:
This change has now been merged. iOS 12, 13 and 14 devices will now be shown the basic HTML view. We continue to support iOS 15.7+.
The upshot is that Discourse forums won’t work on iPhone models older than iPhone 8 (released in 2017). The still-popular iPhone 6 and 7 models can’t be updated past iOS 12.6 IIRC. iPhone 8s can still be updated to the most current version of iOS (16.3).
There were issues here early today - nothing was loading and texts were timing out. I restarted it fiddled with wifi and data then gave up for a time. My Wordle group texted me and of a sudden it was fine again.
IP 12.
See if we can’t invite @codinghorror to swing by and comment.
Same problem here, but different platform. I got the same message on my older Kindle Fire (Silk browser) last night. I don’t know what changed from the prior evening when the SDMB was working fine. I have been trying to update/change the browser on the device, but’s it’s been pretty fickle.
iPhone with Safari here, no messages or errors. Everything is fine.
It’s a 13 Pro Max with an updated iOS, maybe that’s why.
Mine has stopped working. (my browser “is unsupported,” it says) My solution is to stop using my phone to access the SDMB, which is probably something I should do anyway.
That’s what I’ve decided to do. And maybe subscribe to some publications online that I’ve been thinking about, to replace the SDMB when I’m away from home. I can still access the SDMB from my laptop.
When I eventually replace my phone, I’ll make a note of compatibility with Discourse.
FWIW my phone is an iPhone SE, 2nd generation, and the iOS version is 14.7.1. From @gnoitall’s link:
Note that from January 2023, we will go back to supporting only the latest iOS (currently iOS 15). We’re making a temporary exception for iOS 12 because some devices cannot be updated any higher (e.g. iPhone 5s/6).
Which seems to answer my question.
IIUC if my phone updates to iOS 15 while it’s still the latest version (I have it set to automatic updates) the problem may go away by itself.
Thanks for all the help.
I wonder what change happened the other day that started all this? Does anyone know what changed?
Yes – see gnoitall’s post #9 above.
Short answer: a planned end-of-life change in Discourse which apparently just took effect. Discourse code checks for browser version when you connect and if the browser has been designated as “out-of-date”, Discourse displays a non-Javascript view.
The recent change designates all browsers in iOS 12, 13, and 14, as out-of-date.
Since the iOS version you run is limited by what iPhone hardware you use, the change effectively kneecaps using Discourse on older iPhones (anything older than an iPhone 6s).
Yeah, I saw that but skipped over it since I do not use an Apple device or Safari.
Thanks - this makes sense. Odd thing is this happened about a year ago on my very old Kindle Fire and I remember trying to resolve it by installing a new browser, but was unsuccessful (as I am now). But, a few days later, SDMB was working again, and had since, until the other day.