At first time we faced with this problem on 1.0.4 ...
# android
d
At first time we faced with this problem on 1.0.4 and do update to 1.1.0-M2. Issue temporary dissapear. But today we faced with it again.