A solution is in the works, but it won't be immediate because it will need to pass through our QA process and since it was not a planned update it is back in the queue. It may be a couple of months before a public build is available.
You may be able to contact support to get a replacement for the file that causes the problem. The update was made to: floaters/wa_progress/processing objects/ shared.js.
Although we don't like to give out files before complete QA is done, I believe they can send you the file with a disclaimer that it may not work to help a customer when the product isn't working for them entirely. I'd try to post a support incident and ask for an updated version of that file if you can't wait a couple of months for the update to be live.