Closed this issue 8 months ago · 1 comments
upgrade to 2.1.0 to see if this problem has been resolved