Follow this link for a temporary work-around for this issue. We are working on a solution.