You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, not all existing fragments are properly clearing their view bindings when the view is destroyed. This can lead to memory/resource leaks, especially in cases where the fragment lifecycle outlives its view lifecycle.
Identify fragments where bindings are not being cleared
Update those fragment using the following approach:
override fun onDestroyView() {
super.onDestroyView()
_binding = null
}
Currently, not all existing fragments are properly clearing their view bindings when the view is destroyed. This can lead to memory/resource leaks, especially in cases where the fragment lifecycle outlives its view lifecycle.
⚙️ Resources
Important
Don't forget to follow all comments described in the issue: branch name, defined approach...
TASKS
nullall bindings inonDestroyView()method