This is a known bug in this version, but it's already fixed in the next one(0.1.10). Just wait a little bit the next update releases on the 16th!
Thank you for the quick response and keep it up!
