Hi @Lokyord,
Thank you for your clarification. We have successfully reproduced this bug and will address it in the next version.
No need to apologize; your English is clear, and we appreciate your feedback!
Thank you!