Fixed via:
Updating to latest version will fix this issue for you @Kartoon. Thanks for bringing this in our notice.