iOS Safari and v9.3

[lascala_2a3]

I recently updated Moode from v8 to v9, and I'm having issues getting moode.local to load in Safari. I cleared the cache and got it to load once. And if I restart the RPi4 it will load once, slowly. Other browsers on iOS will load the page but they also seem slow. It loads on MacOS Safari, but hesitates a couple seconds and then loads normally (fast). I found a thread from several years ago where someone was having a similar issue, and it was something to do with the type of javascript (lazy load). Moode v8 did not have this issue. I am running a different ad blocker (Ad Guard) but I've tried turning it off and it made no difference. 

So has anyone experienced this and figured out how to fix it? I use the iPhone as my primary interface (Safari as my preferred browser) and I'm hoping to make it fast and smooth.

I'm on iOS 18.3.2., iPhone 15 Pro Max, and Moode v9.3.0. RPi4b 5G wifi

Thank you any insights-

[SerbJ]

I recently loaded Moode 9.3 on two Pi 4Bs.  I haven’t had any display issues using an 9th gen ipad.  I am one s/w release back from the very latest.  Album view is just as fast as it was on ver 8.  The config screens are slower than album view, but seemed about normal.  There is a parameter to change to make them go a little faster, if you are doing allot of changes and testing.  I doubt it matters, but I have just been using the IP address of the Pi.

PS: On the 5G Wi-Fi

[swizzle]

preferences > appearance > native lazyload > no

I’m not sure why it’s broken under iOS but it has been for a while and non-native is just as fast so…

If your router doesn’t change client ips often you might also want to try using the actual ip address to skip the os resolving function (so it’d be like http://192.168.4.39 or whatever instead of http://moode.local).

[Tim Curtis]

Native lazyload is working ok on my end with IOS 18.3.2

[lascala_2a3]

preferences > appearance > native lazyload > no

I’m not sure why it’s broken under iOS but it has been for a while and non-native is just as fast so…

If your router doesn’t change client ips often you might also want to try using the actual ip address to skip the os resolving function (so it’d be like http://192.168.4.39 or whatever instead of http://moode.local).

I tried that and it worked, amazingly. So what would be preventing it from resolving moode.local? Also, it's not resolving in other browsers on iOS now. It's strange how it sort of works sometimes and then doesn't, as opposed to either work/not.

[swizzle]

Native lazyload is working ok on my end with IOS 18.3.2

It’s the same speed as the javascript version? Maybe it’s a library size thing or some markup that was fixed in later versions but non-native on my 8.3.9ish version moode is much faster to the point I’m not sure native is even working.

About moode.local vs the ip address I noticed this with Spotify connect (or rather connect would stop working periodically - which I just assumed was a bug that got fixed in newer versions but am too busy to deal with right now) and the pi stopped responding even with my ssh app. Randomly I found the ip address still worked for ssh so I changed the Home Screen link to use it too. Is it an iOS bug or a piOS bug or something else who knows but using the ip address seems to have fixed things and maybe is a little faster. This is with 18.4 on a 16PM though I changed things a few update versions back.

[Tim Curtis]

I was testing with ~400 albums/5000 tracks  and no diff between native and js on my iphone14. But thats not really much a load test...

Home network issues can be a challenge to troubleshoot especially when they are intermittent or occur only after some long period of time. Theres a lot of potential suspects for "host not found" :-0

[suzywong]

Set a static IP on the RPi, then use that IP in Safari.

Been doing it this way for many years, from my iPad.

Lazy loading is enabled.

IOS 18.3.2 MoOde 9.3

[ils1974]

2701 abums, 29735 tracks. No difference in lazy loading or not. Tested on several devices, amongs them, some iOS devices.

[TheOldPresbyope]

On accessing your player via symbolic <hostname>..local mDNS address versus numeric IP address,

This may be unrelated to the problem(s) expressed in this thread, but I had problems with my player (assume it's named moode) coming up variously as moode.local, moode-2.local, etc.[1] 

This turns out to be a known problem with Linux and the mDNS resolver avahi. Apparently there is a possible race condition with multiple interfaces such as with both IPv4 and IPv6 interfaces enabled in moOde (I have both IPv4 and IPv6 service through to the Internet). I pointed out what I had learned in my Google searches to Tim and he recently modified moOde as a result.

If you go to m > Config > System and scroll down to the Networking section, you'll see the new-ish mDNS discovery setting. By default, it's set to "IPv4 and IPv6 (default)" but it can be changed to "IPv4 -only".

Changing this setting on all my players has seemingly fixed my particular problem. I'm curious if it is of any help for the users posting to this thread.

Note - just yesterday, I came across a post elsewhere which suggests that librespot's discovery code may be another contributor to the problem. In my case, only the change Tim's already made was necessary but YMMV.

Regards,
Kent

[1] As it happens, I have no local DNS resolver running on my LAN so mDNS is all that matters to me.