DGrinev wrote:After a brief discussion QA team confirmed the bug and told me it has been fixed in the upcoming update 3.
However, if you don't want to wait till next update, you can contact the support team, they should have a workaround. Thanks!
DGrinev wrote:Hi and welcome to the community!
There is no way to fix it by the instructions, but as I mentioned before, our technical support has a workaround.
Do not hesitate to contact them and ask for a "fix". Thanks!