Site not visible on an old iPAD 2 device - problem on Safari

[ovimar]

Describe the bug
A clear and concise description of what the bug is.

After update to 14.0.3 and after release of last IOS version some features in my old tablet are disabled.
Now I cannot access Nightscout app or direct link in Safari. (I tried also using other internet browsers but there are few supported by 9.3.5 IOS)
On screen is a general message "loading the client".
(everything is perfect on a more recent iPAD)

IPad with problem : model A1396
IOS version: 9.3.5 (13G36)

NS site: 14.0.3

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Your setup information

• What version of Nightscout (e.g. 0.10.3)
• What type of CGM, and how do you get your data there? (e.g. G4 and ShareBridge, or wired receiver, etc.)
• Is your issue specific to a browser (Firefox/Safari/Chrome?) or a device (Android phone, etc.)?

Additional context
Add any other context about the problem here.

[ovimar]

Clock view of NS is working :). I just discovered and we can still use old iPAD for a while.

[ArthurusDent]

I seem to have the same problem. There wasn't a problem maybe a week or two ago. I have tested it with Safari (Safari/601.1 and AppleWebKit/601.1.46), Chrome (62.0.3202.60), Firefox (7.5 (3349)), and Opera mini (16.0.4). There is a caveat, though: except for Safari, I do not remember whether it ran on any other browser. But it did work with Safari.

Nightscout 14.0.6
iPad 2 (A1395)
iOS 9.3.5 (13G36)

[sulkaharo]

So, sadly the debugging of iOS 9 devices has been deprecated a year ago and someone with an old MacOS installation would need to check what's causing this

[inventor96]

I would hate to exclude anyone, but at some point it's just not feasible to support old software and hardware that the developer/manufacturer doesn't support themselves... Is there a standard threshold for Nightscout @sulkaharo?

[sulkaharo]

Well we've tried to keep NS compatible with old gear, as that's user friendly, and the sources are thus transpiled to be compatible with old Javascript interpreters. It looks like we've inadvertently made some change somewhere in the sources that are not transpiled that renders NS incompatible with iOS 9, but fixing this is really difficult due to the above mentioned issue where Apple has stopped supporting even debugging iOS 9 devices and thus we can't get the exception that's causing this out from the device. So as is, it's very hard to do anything about this unless we find someone with an old Mac and Safari debugging skills, who can pinpoint us where the problem is.

[sulkaharo]

Can you test release 14.0.7 if this works?

[ovimar]

hello. Can you help me? I did something wrong and I cannot update my CGM fork at all. every time it try to update the main nightscout site :(

Please help me!

O

[inventor96]

@ovimar I recommend you use the updater tool at https://nightscout.github.io/pages/update-fork/

On a side note, it's usually a bad idea to include your personal email here, because everyone on the internet can see it.

[ovimar]

i know it is a bad ideea ... to share email ...but i do not know how to solve it.
I'm trying to use updater tool ...but it is an error message and I cannot solve this.

[psonnera]

Try to redeploy https://nightscout.github.io/update/redeploy/ and check this if you have problems https://nightscout.github.io/troubleshoot/troublehoot/#github-and-heroku

[ovimar]

I succeeded to delete my repo ...and to clone last NS repo. Unfortunately old IPAD is not functioned still. Only Clock view is available.

[t1dpanic]

I think I am having the same issue. I use an older iPad with the Nightscout IOS app in guided access mode (always on display!). It now gets stuck on "Loading the client". After reading this thread I opened up my Nightscout site directly in safari with the same issue.

I updated to 14.0.7 this morning, didn't make any difference. My site works fine in Chrome, however Chrome won't run on the old iPad. Going to look at trying other browsers but would prefer if I could get the Nightscout app to work again (via safari).

EDIT: If anyone is aware of a browser that will install on IOS 9.3.5, let me know and I'll try it... Chrome, Firefox, Edge will not install.

[t1dpanic]

With respect to debugging - does anyone have a Browserstack subscription? I used to have through work, but right now I'm limited to the 1 minute trial.

Here's some info that might help (even a little):

In the 1 minute I am given I can only load up my site and take a quick screen grab of the console. This is with Safari 7.1 (Mavericks)

Maybe someone else can get further with a trial or full subscription.

The issue also occurs on:
Safari 8 (Yosemite)
Safari 9.1 (El Capitan)
Safari 10.1 (Sierra)

The issue does NOT occur on Safari 11.1 (High Sierra) or later.

[brainopera]

I thought it was just me with my iPad mini 1. I went to get an iPad mini 2 with the newer iOS 12, but run into the same issue as folks above. Wishing the iPad mini-s could still work as I have them around the house mounted for convenience.

Happened to get a 6th Gen iPad with iPadOS / iOS14, and that works fine in both Nighscout app and browser mode.

FWIW, I did update Nightscout using the updating tool but aftr successful deployment, no dice on the iOS 9 and iOS 12 fronts for iPad mini 1 and 2.

[ovimar]

after .com termination i added /clock/by15-tm30-nl-sg40-ag6-dt14-ar30 and i still use my old iPAD. It is something, not perfect ...but current value and trend can be displayed.

[ArthurusDent]

I haven't noticed any change since updating to 14.0.7.

[thomcost]

This error is not isolated to iOS. Same error when using an older Microsoft Surface with Internet Explorer. This is a nodejs issue I assume.

[sulkaharo]

Can someone here test DEV if it works now

[t1dpanic]

@sulkaharo Just deployed dev and it seems to be working (iOS/Safari 9.3.5 as well as from within the Nightscout app on iPad). Note - for anyone else who tries this, I had to fully clear the Safari browser cache and restarted the device. Without clearing the cache it was not pulling the change on reload of my Nightscout site. Thanks @sulkaharo !!

[ArthurusDent]

I can confirm that it works again on 14.2.2 MASTER and 14.2.3 DEV with Safari, Chrome, Opera mini and Firefox.

[robster7674]

I still see the issue with 14.0.4 on old iPad running iOS 10. I will try to setup a vm using VirtualBox on my MacBook, using the El Capitan iso downloaded from https://archive.org/download/macos-collection/Releases/, and instructions on https://andypi.co.uk/2016/10/31/mac-osx-el-capitan-on-win-10-virtualbox-host/. I'll also test using 14.2.5.

Edit: it works using 14.2.5 (as well as dev 14.2.6), iOS 10.3.3, model MD510NF/A. @sulkaharo: Is debugging Safari still necessary?

[PieterGit]

@ovimar is ios 9 support still needed? ios 9.3.5 was relased August 25, 2016 and ios 9.3.6 (13G37) was released July 22, 2019; 3 years ago.

@sulkaharo : I'm back... Yesterday I did some refactoring to browserslist integration, see #7514 . I now see that ios_saf 9.3 is not in the config and it ios_saf 10 was in the package.json.

Can I summarize the Nightscout iOS support statement as:
"Well we've tried to keep Nightscout compatible with older iPads (Safari on iOS), as that's user friendly. But note that those devices are not supported by Apple anymore and have known security issues. Debugging these old devices gets harder.".

Note that ios9 and ios10 now have a very limited audience (0%), see
https://browsersl.ist/?q=%3E+0.4%25%2C+ios_saf+9.3%2C+ios_saf+10.3%2C+ios_saf+13.7%2C+ios_saf+14.8%2C+not+dead%2C+not+and_uc+12.12%2C+not+ie+11%0A (0%) or https://developer.apple.com/support/app-store/ (iPadOS 13 and earlier, 3%)

[sulkaharo]

I think the general wish for iOS 9 is people still have old devices they've been using as secondary screens for Nightscout. The compatibility broke some time ago and due to Apple not supporting debugging the old devices on Macs that have been updated during the last few years, I could not find any developer who was able to pinpoint which Javascript file is incompatible with the old devices. So given it's practically impossible to test with these devices, I'd just drop the support.

[PieterGit]

I still had an iPad 2 16GB Wifi + 3G white (MC982NF/A) with iOS 9.3.5 and just checked: I can use Nightscout with #7514 and didn't find errors. I would not call it very quick and don't intend to use it but it seems to work.

@ovimar (or others). Can you test if #7514 also work for you on iOS 9 or 10+ older devices. And report back?

I think this issue can be closed and marked as fixed when we decide to merge #7514 to dev.

[LostOnTheLine]

So I get the same Loading the client stuck message, but not on an iOS device.

I have at times got the error on Chrome running on Windows. I have noticed that it will work fine in an incognito tab but even a [CTRL]+Refresh or a delete of the cache data doesn't make it work. After enough time it will start working again. I have tried closing Chrome & reopening it, Restarting the PC, clearing browsing data, etc, all to no effect. I assumed it was a problem with my Chrome as when I'd check the same page in incognito or a different browser or my phone it always worked.

It's now a bigger deal because I have the same problem on yet another device. I have a Proxmox server running on a laptop & I set it up with xscreensaver to show a webpage of my nightscout site. It cycles between the main page & 6 different watch-page versions & 2 instances of https://blackscreen.app. I do this so that the screen doesn't get burn-in, with each of the watch pages using different font sizes & NewLines to change the position of the reading on the screen, which unfortunately can only move up & down, & having a full display, with occasional 10-minute blocks of blank screens.

It has been working well with this setup, & every time the page loads it seems to be loading it fresh, not from a cache or cookie setting, as I have those disabled & it looks like a fresh page not the updating when you reload a page. (I note this only incase it helps diagnose the problem) but for the last 2 days it has been sticking on the Loading screen when trying to load the non-watch page. I've tried restarting the server it's running on, restarting the docker Nightscout, refreshing everything I can, but nothing seems to be working. replacing the URL with another one that goes to the same place works fine.

This makes me believe that the issue is somewhere else, but I cannot say where exactly.

Some interesting things to note

• I created another domain to use it with thatguy.nightscout.mine & it worked on that one while my original one thisguy.xdrip.yours still didn't work, even though they are pointing to the exact same place.
• Just like in Chrome if I switch to the other site it works again
• In Chrome I have had both sites at different times have the same problem, but one always works when the other does not, but other times both work fine.
• xDrip uploads to the same address, the same as used for my original one, without problem even when that same website will not load properly in Chrome or in xScreensaver.

Hope that helps find a solution

[EasternPA]

I just started experiencing this after an apt update and upgrade. I'm using Docker Compose to run two complete NS instances with Cloudflare pointing both public URLs to NPM. Oddly enough, both instances work fine when hitting the UI ports exposed to my internal LAN from Docker but only one works when hitting the public URLs hosted by Cloudflare and routing to NPM. It's not like I have a name resolution error since I'm getting the hung loading screen. Not sure why one would work after a reboot but not the other with both in the same Docker Compose stack. Puzzling.

Brave on Ubuntu 24

Update: I have multiple FQDNs pointing to each instance. A different FQDN pointing to the failing instance is working fine.

Update 2: I went away for a few days, and the issue was resolved upon returning. I did not make any changes to my configuration.