Thanks @Luiz D'Aniello we fixed it in our internal build a couple of days ago. A new fixed version will be available soon. Thanks!