We're aware, and hoping to have a solution to the problem with our next update (coming Monday approximately!)
