No reason to have automatic updates *while in use*

why on earth would you design it to update apps while they are in use?
why is it even a feuture of the app if your going to wipe everyones in-progress projects without warning?
how could you not realize thats whats going to happen by allowing updates while in use? theres not even any indication that is what is going to occur.
‘automatic’ implies automatic, not full app-restarts at random.
and if this is a bug, then i’d highly suggest making it only automatically update at a set time, so this never happens again.
if it happened to someone in a much more vulnerable position than me i imagine they’d be far more pissed off.

Where is your common sense? I am guessing it is about F-Droid app, but instead of being irritated, provide better details and logs/snaps, detailed information.

Because we used the other method and long living apps were never updated…

See Gentle update API - F-Droid shows endless update when update is started while foreground service of the app to be updated is active (#2919) · Issues · F-Droid / Client · GitLab

The smart solution to that would be a nag prompt advising the user to save their work and allow the app to be updated.

We want a smart solution, feel free to open a Merge Request with this code change for us to test too.