Some kind of workaround for the problem has been implemented… so, it may start to work with the next update