Thanks for reporting the problem, we'll publish a fix as soon as possible (probably tomorrow). Sorry for the inconvenience.
Edit: v1.0.0f with a fix has been published, let us know if everything works fine.