Could you check if this bug stops in build 2.0.10b, please?
Can confirm it is fixed :) Thank you.
Thanks for letting us know.
