title: How ViewModel survives configuration change
body: <p>I am trying to use ViewModel in my app. The question comes to my mind is How View Model survives configuration changes. I read number of blog posts saying that " </p>
  
  <blockquote>
    <p>It will create a <strong>HolderFragment</strong> to add to your activity or your
    fragment, it's invisible, when the configuration changed, activity
    destroyed, but holder fragment is still alive</p>
  </blockquote>
  
  <p>and that make sense.But I tried to explore more on this and found out that in <strong>support library  27.1.0+</strong> they have removed the HolderFragment with  Description saying</p>
  
  <blockquote>
    <p>Deprecate ViewModelStores.of() and the <strong>HolderFragment it relies on
    as they are no longer needed</strong> <a href="https://android.googlesource.com/platform/frameworks/support/+/5122b0151b549a81b0c8cac9192b6713df0d81ab" rel="noreferrer">link for android.googlesource</a>.</p>
  </blockquote>
  
  <p>Now the question is How they are doing the same thing right now?</p>