Does anyone know why the `onDestory` function of a fragment wouldn’t be called when closing the app ...

# android

[Elyes]

Does anyone know why the onDestory function of a fragment wouldn’t be called when closing the app ?

[Sean Keane]

is it called when you kill the app from the background?

[Elyes]

no

[Sean Keane]

Is on pause?

[Elyes]

it is

[Elyes]

But it’s also called when the app just goes to background. So it’s not indicative of whether the fragment was destroyed or not

[Kris Wong]

https://developer.android.com/reference/android/app/Activity#onDestroy()

[Elyes]

I’m having a problem with the Fragment’s onDestroy not the Activity’s

[Sean Keane]

As far as I know, onDestroy() is not guaranteed to be called unless you explicitly call onFinish().

[satyan]

Also, if you use setRetainInstance(true) , onDestroy won’t be called 🙂

[satyan]

And fragment’s onDestroy is linked to its Activity’s onDestroy so the link from @Kris Wong is relevant:

There are situations where the system will simply kill the activity’s hosting process without calling this method (or any others) in it, so it should not be used to do things that are intended to remain around after the process goes away.

[Elyes]

Alright, thanks for the insight guys