Hello everyone (@here),
We’re happy to let you know that this issue was fixed with the v0.9.0 update.
Thank you for your patience while we worked on a fix, and we also appreciate you taking the time to submit a report and help us investigate the issue.
If you continue to experience similar problems after updating, please let us know in a new thread.
Thank you.