UPDATE 2:
Thank you for the report! We've fixed the super critical issue and published a new version (1.6.3). If you have a chance, please try it again.