We managed to reproduced the issue, and there will be a fix in the next version. Thanks for your feedback.