@zatz
This should be solved now. The solution is here with our latest update. Thanks for your report!