This error occurs on iOS 26.0 -> 26.0.1. By version 26.1, the problem no longer exists, perhaps Apple has fixed it. Can you confirm for me that Apple fixed it correctly? And is there any note about whether this bug has been fixed?