Confirmed…iOS 18.1 fixed this issue

yeah - no one seems to focus too much on it. There's clearly an issue but "filing a feedback" doesn't help...did that, looking for an actual acknowledgement of the issue from Apple and I guess timeline for a fix

i'm seeing the same issue - now that I think of it it did start after moving to iOS 18. Has anyone come up with a root cause/approach to solve this?