Hi everyone. (@here)
The issue has been partially fixed through v0.5.3 update, but it may reoccur under certain conditions. If you are still experiencing this issue after the update, please report it again. Thank you!
8 Likes