Looks a lot like this topic:
The issue had appeared for some when updating to 2.6.0.beta2, others to beta3.
After updating to beta4 and rebuilding the app, the issue disappeared, and didn’t reappear after updating to beta5. So perhaps try updating to beta6 and see, otherwise wait for further updates, it may get solved at some point.
Have seen the same issue, on Meta as well, doesn’t seem logical to me.