Hello, this problema is now fixed in v1.0.6. Thanks for reporting this issue and sorry for the inconvinience.
