Hi, thanks for reporting this! The fix for this issue will be available in version 1.1.1, released prkbably this friday.
Thank you for your patience!
Thank you. <3