Android架构组件：返回Fragment后ViewModel onChange多次触发致重复创建Fragment

Hey there! Let's break down why your onChange() is firing multiple times after navigating back from BlankFragment and fix this issue step by step.

What's Causing the Multiple Calls? #

The core problem here is likely tied to LiveData's behavior combined with repeated observer registration, or the fact that LiveData retains the last emitted value. When you navigate back to FragmentExample, if you're re-registering the LiveData observer (either explicitly or implicitly), LiveData will immediately deliver the last value again. Plus, if old observers weren't properly cleaned up, multiple observers will trigger the onChange() callback at once.

Fixes to Try #

1. Use viewLifecycleOwner for Observer Binding

Always bind your LiveData observer to the Fragment's view lifecycle instead of the Fragment itself. This ensures the observer is automatically removed when the Fragment's view is destroyed (like when navigating away), preventing stale observers from lingering.

// In FragmentExample
repository.yourInputLiveData.observe(viewLifecycleOwner) { input ->
    handleInput(input)
}

2. Add a Flag to Prevent Duplicate Navigation

Add a simple boolean flag to track whether you've already navigated to BlankFragment, and reset it when the Fragment returns to the foreground.

private var hasNavigated = false

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    
    button.setOnClickListener {
        val input = editText.text.toString()
        repository.submitInput(input)
    }

    repository.yourInputLiveData.observe(viewLifecycleOwner) { input ->
        if (input == "0" && !hasNavigated) {
            hasNavigated = true
            // Perform Fragment replacement
            parentFragmentManager.beginTransaction()
                .replace(R.id.your_container_id, BlankFragment())
                .addToBackStack(null)
                .commit()
        } else if (input != "0") {
            Toast.makeText(requireContext(), "Invalid input!", Toast.LENGTH_SHORT).show()
        }
    }
}

// Reset the flag when the Fragment comes back into view
override fun onResume() {
    super.onResume()
    hasNavigated = false
}

3. Use a Single-Event LiveData for Navigation

LiveData is designed to hold state, not fire one-off events like navigation. For actions that should only happen once, create a custom SingleEventLiveData to ensure events are consumed only once, even if observers re-register.

First, define the custom class:

class SingleEventLiveData<T> : MutableLiveData<T>() {
    private val pending = AtomicBoolean(false)

    override fun observe(owner: LifecycleOwner, observer: Observer<in T>) {
        super.observe(owner) { value ->
            if (pending.compareAndSet(true, false)) {
                observer.onChanged(value)
            }
        }
    }

    override fun setValue(value: T?) {
        pending.set(true)
        super.setValue(value)
    }

    fun postEvent(value: T?) {
        pending.set(true)
        super.postValue(value)
    }
}

Update your Repository to use this class:

class Repository {
    private val _inputEvent = SingleEventLiveData<String>()
    val inputEvent: LiveData<String> = _inputEvent

    fun submitInput(input: String) {
        _inputEvent.setValue(input)
    }
}

Then observe the event in FragmentExample:

repository.inputEvent.observe(viewLifecycleOwner) { input ->
    if (input == "0") {
        // Navigate to BlankFragment
        parentFragmentManager.beginTransaction()
            .replace(R.id.your_container_id, BlankFragment())
            .addToBackStack(null)
            .commit()
    } else {
        Toast.makeText(requireContext(), "Invalid input!", Toast.LENGTH_SHORT).show()
    }
}

Quick Checks to Rule Out Other Issues #

• Make sure you're not calling observeForever() anywhere—this method doesn't bind to a lifecycle and requires manual removal with removeObserver().
• Verify your Repository isn't accidentally emitting the input value multiple times (e.g., calling setValue() more than once per button click).

内容的提问来源于stack exchange，提问作者Nikolas Bozic