we've identified the issue and are working on a fix, thanks for reporting!