We’ve found the cause of this problem and we’ve got a fix for the next update. Please see the workaround in this post: