Voyager

Yeah, it's solely Voyager's fault (or at least the underlying cross-platform frameworks it's built upon). Gracefully handling Android lifecycle events so this sort of thing doesn't happen was literally the first topic covered in the Android documentation back when I learned it. Android provides plenty of tools to save and restore state when an activity is destroyed, but I guess it's hard to hook into them when the Android app is just a wrapper around an embedded web app?

Voyager is the only Fediverse app I've tried that has this problem, for the record.