[PROBLEM] UI hangs on phone while browsing library

[Tim Curtis]

Thanks, I'll try to get hold on a Mac and follow the steps, and report back if I come to some conclusion.

Meanwhile I've been able to put some system into all this mess. I remembered that my phones both had a software update to IOS v. 18.3  last week, which coincides with the onset of problems. Then I looked at my wife's and daughter's phones, and luckily they have IOS 16.1 and 17.3, respectively.
The problem does not occur with them, everything works flawlessly as ever before on both Chrome and Safari browsers!!
So on one hand, it's almost sure to be an IOS related problem, maybe some tightened network security policy code option, or simply a bug in the updated browser engine. On the other hand, I'm not sure that you, as the Moode developer could (or should) devote any time to that, when it could very well be resolved already in the next IOS update.

Mine is IOS 18.1 but I can update to 18.3 and re-test.

[mario74m]

Mine is IOS 18.1 but I can update to 18.3 and re-test.

Well, I just looked at Apple's IOS update release notes. Under 18.3, which is a security release, they have several remarks regarding WebKit, which (if I remember correctly) is used by all browsers on IOS, so that explains why both Chrome and Safari exhibit the same behaviour. So, among the patches which could potentialy be connected with the problem there's a patch for CVE-2025-24158 (Impact: processing web content may lead to DOS, Description: the issue was addressed by improved memory handling), a patch for CVE-2025-24162 (Processing maliciously crafted web content may lead to unexpected process crash. The issue was addressed through improved state management). There's also 4 similarly described CVE-related WebKit issues in the release notes of IOS 18.2.

 Maybe something in the manner the page is being served misleads the patched browser engine into thinking it's malicious so it just breaks it before it loads completely, or prohibits it from rendering completely. Just a wild guess...

[Tim Curtis]

Mine is IOS 18.1 but I can update to 18.3 and re-test.

Well, I just looked at Apple's IOS update release notes. Under 18.3, which is a security release, they have several remarks regarding WebKit, which (if I remember correctly) is used by all browsers on IOS, so that explains why both Chrome and Safari display the same behaviour. So, among the patches which could potentialy be connected with the problem there's a patch for CVE-2025-24158 (Impact: processing web content may lead to DOS, Description: the issue was addressed by improved memory handling), a patch for CVE-2025-24162 (Processing maliciously crafted web content may lead to unexpected process crash. The issue was addressed through improved state management). There's also 4 similarly described CVE-related WebKit issues in the release notes of IOS 18.2.

 Maybe something in the manner the page is being served misleads the patched browser engine into thinking it's malicious so it just breaks it before it loads completely, or prohibits it from rendering completely. Just a wild guess...

No issues whatsoever testing with 18.3 IOS on my end. All folders are rendered in the list.

I can never rule out a bug in moode code but we need to have a repro by someone first in order to go to the next step which is to obtain some error logs that indicates what might be happening. Otherwise yes, its just a wild goose chase.