Hi @sunny,
Thank you for reporting this.
This was fixed with 1.4.0.2:
Kindly let me know if this is the case on your end. Thank you in advance.