Thank you. We've spotted that and already fixed it in our internal releases. We'll deploy a new build with many fixes soon.