Hi @yankiara,
Thank you for taking the time to report this!
This should now be fixed with 1.3.2.1. Kindly let me know if this is the case on your end.
Thank you in advance.