This is a known bug and is said to be fixed with the next update. (v1.1 is planned to be released at some point during April.)
Cool! Thank you!
