Thanks for the report, we have this identified as a known issue and we're working on it.