@curmi - Looks like the issue has been fixed in iOS 16.1 beta 4. Yay! 😀