From b56f2679790240105be4ac803dce0099c6595fa1 Mon Sep 17 00:00:00 2001
From: Kirill Kamakin <k.kamakin@protonmail.ch>
Date: Sat, 2 Apr 2022 18:12:32 +0500
Subject: [PATCH] Use viewLifecycleOwner to observe auth status

Even though views aren't modified when auth
status changes, we still need to operate
only when view is visible.
---
 .../java/gq/kirmanak/mealient/ui/recipes/RecipesFragment.kt     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/src/main/java/gq/kirmanak/mealient/ui/recipes/RecipesFragment.kt b/app/src/main/java/gq/kirmanak/mealient/ui/recipes/RecipesFragment.kt
index d7fa772..ecb1696 100644
--- a/app/src/main/java/gq/kirmanak/mealient/ui/recipes/RecipesFragment.kt
+++ b/app/src/main/java/gq/kirmanak/mealient/ui/recipes/RecipesFragment.kt
@@ -40,7 +40,7 @@ class RecipesFragment : Fragment(R.layout.fragment_recipes) {
         super.onViewCreated(view, savedInstanceState)
         Timber.v("onViewCreated() called with: view = $view, savedInstanceState = $savedInstanceState")
         setupRecipeAdapter()
-        authStatuses.observe(this, authStatusObserver)
+        authStatuses.observe(viewLifecycleOwner, authStatusObserver)
         (requireActivity() as? AppCompatActivity)?.supportActionBar?.title = null
     }