From support on May 5, "...the situation is caused by an issue that has already been acknowledged by our development team. We are currently working on a fix that will be done by means of an automatic update and won't require any additional action on your end."