title: Why would a LiveData observed with viewLifecycleOwner get callbacks after onDestroyView?
body: <p>I have a Fragment that’s using View Binding, so it sets its <code>_binding</code> member variable in <code>onCreateView</code> and nulls it out in <code>onDestroyView</code>. In <code>onViewCreated</code>, I observe a LiveData from the view model using <code>viewLifecycleOwner</code> as the LifecycleOwner. (In reality this is split between a fragment and a base class, but I can’t see how that would explain any of this)</p>
  <p>I can’t reproduce this in house, but crashlytics is reporting cases in the field where the LiveData’s observer is getting called back when the binding is null, making me think that somehow it’s being called after <code>onDestroyView</code> has been called. Any idea how that’s possible?</p>
  <p>UPDATE: Turns out the observer was calling postDelayed on one of the views, so the Runnable was being executed (and accessing the binding) after onDestroyView had been called.</p>
  <p>Thanks to @Zain and @EpicPandaForce for taking a look.</p>