Thanks for reporting. We have traced & solved this issue. We can confirm that the next updatewill address this.