Hi Biscuit, we’ve talked about this issue briefly here:
We’ve fixed this recently and it will be in the next release