Thanks for trying. It was worth a shot. We are tracking this issue in this thread here:
You try the workaround here to see if it helps. If not, I would recommend keeping an eye on this thread. Once we have a full resolution for this we will update the thread.