Vechkanov

We are looking into this issue right now, but we need more time. For now we do not see any changes that can cause such issues in update from 4.2.0...