Users reported a UI issue in the Android Discourse app where forum entries jump briefly after opening, particularly when no unread topics exist. Moin shared a video demonstrating the issue and noted it began after a recent update. pmusaraj acknowledged the bug and submitted a fix, expected to roll out via the Play Store in the coming days pmusaraj. Separately, trs80 reported that the app reverted to using Chrome instead of Firefox for in-app browsing — a regression previously discussed in meta.discourse.org. pmusaraj suggested toggling the “Open sites with in-app browser” setting, but trs80 confirmed it didn’t resolve the issue. Further investigation by pmusaraj confirmed the in-app browser is using Chrome instead of Firefox, and trs80 added that authentication also fails due to lack of Chrome integration. pmusaraj agreed it’s likely due to an underlying library update, as code changes between versions were minimal aside from layout adjustments. The team is investigating further.
When I open the app on my Android tablet, the entries jump once shortly after opening when the URL is displayed because there are no unread or new topics. Can this be prevented? I think this did not happen before the recent update.
The video is at half speed:
Thanks for the report @Moin, should be able to fix it.
I have submitted a fix for this, it should be released in the Play Store over the next few days.
This update has reverted to using Chrome instead of Firefox for me, last discussed in Android app doesn't use browser inside the app any more, launches site in full browser - #15 by trs80
I do like the more compact layout of forums now.
If you toggle the “Open sites with in-app browser” setting on and off, does it fix the issue for you?
Nope, still Chrome. I’m guessing some library upgrade caused it since I had a brief look at the history but couldn’t see any relevant code changes.
So, you’re seeing the in-app browser, but it’s the wrong engine (Chrome vs Firefox), is that correct?
That’s correct, and I’m not authenticated either (since I don’t use Chrome)
Ok, I think you are right, this looks like a change in an underlying library. Specifically between the last two Android version, there is almost no change (just the layout tightening). But will closer in any case. Thanks!
This topic was automatically closed after 6 days. New replies are no longer allowed.