We're sorry to hear that! We've uploaded a fix that should hopefully take care of that issue. Apologies for the inconvenience, and please let us know if you run into any other bugs!
