Alas, my enthusiasm was a little bit premature.
While my iPhone running iOS 26 proves that the problem has been fixed, somebody's iPad (though running at the moment iPadOS 18), despite getting the app being compiled and installed from Xcode 26, shows the bug being still there.
How come that iOS 26 does have a fix, but iPadOS 26 does not (I checked on Simulater as well).
Topic:
App & System Services
SubTopic:
General
Tags: