Hey! Both of these issues were being caused by the same bug. Both are fixed in the latest version (1.0.2). Thanks for the help reporting them!
Cool, thank you for fixing the issues so fast.