Hello All,
Thank you for the additional reports regarding this behavior. We believe we have identified the root cause of the issue and a fix is currently undergoing QA testing.
We hope to release this fix to everyone as soon as possible. In the meantime, one of the workarounds mentioned earlier in the thread may help:
We apologize for the inconvenience and thank you again for your patience as we work on addressing this issue. We’ll keep everyone updated as we have more details from our development team, thank you!