I have also encountered this issue. Would waiting for it to be fixed in the next iOS release make sense? Is there a workaround for this?

iOS 18.2 beta 4 doesn't have this issue