Both of the issues you've reported should be fixed in the v1.2.0 update. Thanks again for mentioning them!
