Android中Fragment为何自动保存视图状态？EditText状态异常留存问题

Let's break down what's happening here and walk through actionable fixes for your issue.

Why the Inconsistent Behavior? #

First, let's connect Android's default Fragment view state handling with your custom navigation stack implementation:

• Deep navigation (move/back within a tab): When you push a new Fragment via move() and pop back via back(), the original Fragment instance stays in your custom Stack. When it's replaced out, its lifecycle hits onDestroyView (but the Fragment instance itself isn't destroyed). Android automatically calls onSaveInstanceState here to save view state (like your EditText input). When you replace the Fragment back into the container, the system uses that saved state to restore the EditText content—hence the retained text.

• Tab switching: When you switch tabs via change(), the current tab's Fragment is replaced out, but since it's not added to the system back stack (your code uses replace() without addToBackStack()), Android doesn't reliably preserve its view state. Even though the Fragment instance is in your custom stack, the system skips full state preservation for Fragments removed from the container without being added to the back stack. This is why your first-level tab Fragments lose their EditText content when switching back.

Fixes to Choose From #

1. Manually Clear Content for Tab Switches #

If you want to retain deep navigation state but reset EditText content when switching tabs, add a flag to your Fragments and trigger a clear during tab switches:

Step 1: Add a flag to a base Fragment (or individual Fragments)

open class BaseFragment : Fragment() {
    var shouldClearInput = false

    override fun onResume() {
        super.onResume()
        if (shouldClearInput) {
            view?.findViewById<EditText>(R.id.your_edittext_id)?.setText("")
            shouldClearInput = false
        }
    }
}

Make sure your Fragments (like MemoFragment) extend this base class.

Step 2: Update the change() method in FragmentNavigation

fun change(info: FragmentInfo) = 
    fragmentMap[info.tag]?.let {
        currentTab = info.tag
        if (it.isEmpty()) {
            it.push(info.fragment)
            manager.commit { replace(container, info.fragment) }
            return@let
        }
        // Tell the target Fragment to clear input when resumed
        (it.last() as? BaseFragment)?.shouldClearInput = true
        manager.commit { replace(container, it.last()) }
    }

2. Switch to System Back Stack (Recommended) #

Your custom stack is overriding Android's built-in navigation state management, which causes the inconsistency. Using the system back stack aligns with Android's expected behavior:

class FragmentNavigation(private val activity: MainActivity) {
    private val manager = activity.supportFragmentManager
    private var currentTab = 1 // Initial tab
    private val container = R.id.nav_host_fragment
    
    // Store root Fragments for each tab
    private val tabRoots = mapOf(
        0 to Tab0Fragment(),
        1 to MemoFragment(),
        2 to Tab2Fragment(),
        3 to Tab3Fragment(),
        4 to Tab4Fragment()
    )

    init {
        // Load initial tab
        manager.commit {
            replace(container, tabRoots[currentTab]!!)
        }
    }

    fun change(info: FragmentInfo) {
        if (currentTab == info.tag) return
        currentTab = info.tag
        
        // Clear all back stack entries for the previous tab
        manager.popBackStackImmediate(null, FragmentManager.POP_BACK_STACK_INCLUSIVE)
        
        // Load the target tab's root Fragment
        val rootFragment = tabRoots[info.tag]!!
        manager.commit {
            replace(container, rootFragment)
        }
    }

    fun move(info: FragmentInfo) {
        manager.commit {
            replace(container, info.fragment)
            addToBackStack(null) // Add to system back stack
        }
    }

    fun back() {
        if (manager.backStackEntryCount == 0) {
            activity.finishApp()
        } else {
            manager.popBackStackImmediate()
        }
    }
}

With this setup, Android handles view state preservation consistently. If you want to disable EditText state retention entirely, add logic in your Fragment's onViewCreated to clear the input.

3. Disable Automatic View State Saving #

If you want no Fragments to retain view state, disable it at the view or Fragment level:

Option A: Disable for a single view (e.g., EditText)

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    val editText = view.findViewById<EditText>(R.id.your_edittext_id)
    editText.isSaveEnabled = false // Prevents state saving for this view
}

Option B: Disable for the entire Fragment

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    // Clears input when the Fragment's view is destroyed
    viewLifecycleOwner.lifecycle.addObserver(object : DefaultLifecycleObserver {
        override fun onDestroy(owner: LifecycleOwner) {
            view?.findViewById<EditText>(R.id.your_edittext_id)?.setText("")
        }
    })
}

内容的提问来源于stack exchange，提问作者J.Dragon