Once again, thank you for taking the time to report this @NHViet!
This was fixed with 1.3.1. Kindly let me know if this is the case on your end.
Thank you in advance.