Hi everyone! The engineering team is actively looking into the issue posted by @ufrei.
We are concerned with this problem not less than you're. Unfortunately, we don't know any possible workaround at the moment. Although, we hope that the upcoming application release will be able to help with it a bit.