I just popped out to grab an image for a post, then realized I didn’t have a photo app, then went to the play store to download Ente, then decided I should just download an image directly… by the time I got back, Voyager had been closed and the draft was (apparently?) lost.

Any idea of how to prevent this from happening in the future?

And where is the draft supposedly saved?

  • schipelblorp@sh.itjust.worksOPEnglish
    3·
    2 months ago

    Yes! At least as far as information goes. From the nostupidquestions lemmy (see post history), Voyager isn’t a proper Android app but basically a web page (???), so it doesn’t have the same granular system access an app might and its behavior might be more limitted in that regard, so, yeah, lean on OS solutions here.

    I also got a recommend to try Interstellar.

    But what the heck, let me open a few tabs and get back to you in two minutes.

    Edit: I saved this comment, opened a bunch of stuff, and came back to Voyager saying it closed and that it noticed I was editing but to just “begin composing.” So, yes, I’d say avoid leaving Voyager at all costs while writing or compose in an editor.

    • Quetzalcutlass@lemmy.worldEnglish
      2·
      2 months ago

      Yeah, it’s solely Voyager’s fault (or at least the underlying cross-platform frameworks it’s built upon). Gracefully handling app 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.