Thanks for the info.
That helps. This should be fixed in the latest version (v1.0.6), so please try updating if you're still seeing the issue.
