Thank you. This is a known issue, which should be fixed in the next update (currently being prepared/tested).