This problem is fixed in the upcoming version.
We delayed the releasing (supposed to be last week) of the new version since there was another issue that has to be solved before the release.
All known issues are fixed now and I hope it can pass the testing early this week.