Thank you for reporting this, I’ll investigate this issue!
Update v1.0.4 should fix this issue entirely, once again thank you for reporting this ✌️
