Thanks for posting a workaround for users. We're currently investigating the issue & will report back after we have a fix.