The 11.5.0.1 version in which the bug got fixed was posted on the Playstore on same day. Most likely this would have happened when you were still on the earlier build. The latest build available on the Playstore wouldn't have this issue anymore.
↧
The 11.5.0.1 version in which the bug got fixed was posted on the Playstore on same day. Most likely this would have happened when you were still on the earlier build. The latest build available on the Playstore wouldn't have this issue anymore.