Hey all. We faced this too and we had about 3 screens broken in different ways, and we came up with some code bandaids We investigated and found that something was misfiring (such as an event after requestAnimationFrame was not being fired or was timed differently) and the sizes of components and panels were not properly being set within the javascript context, and so things like animations would not complete properly, leaving components off screen or containers not interactable We worked around this by adding a deferred call to refresh sizes when necessary, into the afterRender or initialize block of the component affected, or the parent component For example, panels were not scrollable, and we found the scroller was never obtaining the size of the container properly, and so the scroller panel was size 0, preventing scrolling We added an afterRender block (deprecated but initialize should do it too) in Container which defers a call to refresh() on the scroller, which appears to have worked around the issue on two screens We also applied a similar fix to another animated card layout component I mentioned requestAnimationFrame because I understand that iOS 18.2 beta enabled some support for 120hz for requestAnimationFrame specifically, so I wonder if this change caused this somehow.