Your comments

I have the same issue.
v2.0 build 2210
How can we fix this?