Ok, I found a path to reproduce it which fits the scenario. This can happen when the app is in the background for some time, and the system decides to kill it to release resources, and then it’s restored either by opening the app or by finding it in the recent apps list. That is why force-closing the app (swiping up from recents) fixes the issue, because then the app is fully relaunched (not restored). We will fix it in the upcoming release 2.2.0.