This appears to be a known problem with v1.2.0 (see the bug report) and has been fixed for v1.2.1. So if you can try the newer release, it should work.