Hello, Thank you for the info, we think we found the origin of the bug. it should be solved for version 1.0.6
