If I’m on a feed, say All, then I accidentally open the communities side bar, I cannot for the life of me work out how to close it without having to choose a feed or community, triggering a refresh.
This is worse when I’m on a post. I am here reading the comments in a post and accidentally open the communities side menu, how do I close it and stay on the post? I have almost no chance of finding that same post again 🙁


I’ve heard of the double back bug (from a post it goes back to the communities list in one swipe) but I’ve never been able replicate it myself.
It anyone has good replication steps please lmk!
I have that happen sometimes when I hit the back button whilst looking at a picture fullscreen.
other times just randomly…
any way to add an option to save your reading place in the feed by default and just a pull down to refresh?
really sucks sometimes when you’re a few
hrsmins scrolling deep only to have it start from the top.If the community side bar could be opened and closed without it refreshing the feed (overlaid instead of a screen change), then the bug would be less of an issue because the impact would be greatly reduced.
If the app thinks the app button is being pressed twice, then the app would just close instead of going to the communities list, so that wouldn’t solve the problem. I need to get the the root of the problem with a reproduction in order to fix it.
Maybe, but I think many people would like the ability to do this regardless of the bug 😅.
Me too. I’ve personally never faced the bug you’ve mentioned myself but I do sometimes accidentally end up opening the communities sidebar and end up losing my place in the feed because I can’t just dismiss the sidebar. I have to select something and that will end up refreshing my feed. If we could just have a close button on the sidebar that would help immensely.
What if there was a setting that would make a toast message come up “swipe again to close feed”?
It would only activate/apply if the thing to swipe to is the communities list.
I’d have to do some testing but that wouldn’t be that hard to implement.
It definitely happens random or after a certain amount of time. Are there any logs produced that could help identifying the probkem?
No logs for something like this.