Thanks for the report. We're aware of this issue and we're currently working on a fix.