Hi, this issue has been fixed for the upcoming update (6.3.0), which will be released in Beta by the end of this week, public release a few days later.