My colleagues also encountered the same problem on 16.0.0. It was fixed in 26.2 beta 2. I'm not sure 26.1. Is there any way to avoid it wihout updating xcode version?