Hey everybody,
We’ve made some edits to the main message to reflect some of the developments about this problem. We’ve also incorporated the workaround by @Illidan you can use before we push a hotfix for this issue. It is currently in testing and will be released as soon as possible.