Thank you very much for reporting this and the detailed description. I have fixed this issue in the most recent update, should be live in the next few days :)
