Thanks for the report, we are aware and we're looking into it. There isn't a workaround so far, that I know of.