Sorry I completely overlooked this issue! Its fixed in the incoming v1.1.3 that should be available later this week.
