It's good to hear you were able to get around it!
We also just released version 2.1 which should include a fix for this issue. Thanks for the help!
