@sunny Thanks for reporting this. Definitely something went wrong with the last update. We have just pushed a fix with 1.2.1.8.1. So sorry for this.