Thank you for letting us know. We have a fix for this in the pipeline and will update the issue when it's released.