Thank you for the report. I have confirmed this issue in the v1.0.1 update. I have rolled back the download to an earlier version, in which this doesn't happen. We'll be working on it!
