Closed tappdesign closed 3 years ago
Doing like that onDestroy will not be called, and could leak something (for example EventBus events will still be received)
I'm going to get the same change you made but trying keeping your app under observation for strange behaviors related to this.
Just a reminder for me: this happens when rotating the detail fragment due to fragment stack containing a destroyed ListFragment
Just open some existing note for edit. Rotate device two times (vertical - horizontal - vertical) and app will crash:
binding
becomes nullpossible fix in this commit: https://github.com/tappdesign/Omni-Notes/commit/148da101db91fb1f3728f30bd5b06937b0004462
as it is advised https://stackoverflow.com/questions/23391837/fragment-oncreateview-and-onactivitycreated-not-being-called-on-rotation
but I'm not sure if this is the right solution....