Yes, we are aware of this issue. Aiming to fix it in an upcoming build.