Hi, the bug has been reproduced and fixed in V1.1 which will roll out shortly. Thanks again for the report.
