Use viewLifecycleOwner as the LifecycleOwner

Question

I have a fragment:

class MyFragment : BaseFragment() {

   // my StudentsViewModel instance
   lateinit var viewModel: StudentsViewModel

   override fun onC         


        

Answer 1

Why I get this error?

Lint is recommending that you use the lifecycle of the fragment's views (viewLifecycleOwner) rather than the lifecycle of the fragment itself (this). Ian Lake and Jeremy Woods of Google go over the difference as part of this Android Developer Summit presentation, and Ibrahim Yilmaz covers the differences in this Medium post In a nutshell:

• viewLifecycleOwner is tied to when the fragment has (and loses) its UI (onCreateView(), onDestroyView())

• this is tied to the fragment's overall lifecycle (onCreate(), onDestroy()), which may be substantially longer

How to get rid of it?

Replace:

viewModel.students.observe(this, Observer {
        //TODO: populate recycler view
    })

with:

viewModel.students.observe(viewLifecycleOwner, Observer {
        //TODO: populate recycler view
    })

In your current code, if onDestroyView() is called, but onDestroy() is not, you will continue observing the LiveData, perhaps crashing when you try populating a non-existent RecyclerView. By using viewLifecycleOwner, you avoid that risk.

Answer 2

Instead of this use viewLifecycleOwner to observe LiveData

viewModel.students.observe(viewLifecycleOwner, Observer {
    //TODO: populate recycler view
})

Answer 3

viewLifeCycleOwner is LifecycleOwner that represents the Fragment's View lifecycle. In most cases, this mirrors the lifecycle of the Fragment itself, but in cases of detached Fragments, the lifecycle of the Fragment can be considerably longer than the lifecycle of the View itself.

Fragment views get destroyed when a user navigates away from a fragment, even though the fragment itself is not destroyed. This essentially creates two lifecycles, the lifecycle of the fragment, and the lifecycle of the fragment's view. Referring to the fragment's lifecycle instead of the fragment view's lifecycle can cause subtle bugs when updating the fragment's view.