求助：ViewPager多Fragment堆叠后按Home返回出现重叠的修复方案

Hey, I've dealt with this exact bug before! The core problem is that when your app goes to the background and comes back, the Android system restores all existing Fragment instances via the FragmentManager—but your registeredFragments SparseArray doesn't get updated to match these restored instances. This causes your code to create new Fragment instances and add them on top of the already restored ones, resulting in that annoying overlap.

Here's how to fix it step by step:

1. Fix Fragment Registration in Your Pager Adapter #

The FragmentPagerAdapter's instantiateItem method automatically restores existing Fragments on recreation instead of calling getItem. You need to make sure your registeredFragments array gets updated every time a Fragment is instantiated (whether it's new or restored):

public class MyViewPagerAdapter extends FragmentPagerAdapter {
    private SparseArray<Fragment> registeredFragments = new SparseArray<>();

    public MyViewPagerAdapter(FragmentManager fm) {
        super(fm);
    }

    @Override
    public Fragment getItem(int position) {
        // Return your root Fragment for each tab as before
        return YourRootFragment.newInstance(position);
    }

    @Override
    public int getCount() {
        return yourTabCount; // Replace with your actual tab count
    }

    @Override
    public Object instantiateItem(ViewGroup container, int position) {
        // Let the superclass handle instantiation (restoring existing Fragments or creating new ones)
        Fragment fragment = (Fragment) super.instantiateItem(container, position);
        // Update your registeredFragments with the actual instance used
        registeredFragments.put(position, fragment);
        return fragment;
    }

    @Override
    public void destroyItem(ViewGroup container, int position, Object object) {
        registeredFragments.remove(position);
        super.destroyItem(container, position, object);
    }

    // Add a helper method to get registered Fragments safely
    public Fragment getRegisteredFragment(int position) {
        return registeredFragments.get(position);
    }

    // Add a method to manually register restored Fragments (for step 2)
    public void registerFragment(int position, Fragment fragment) {
        registeredFragments.put(position, fragment);
    }
}

2. Sync Restored Fragments in Your Activity's onCreate #

When your Activity is recreated (after coming back from the background), you need to re-link the already restored Fragments to your adapter's registeredFragments array. First, make sure your root Fragments store their tab position:

public class YourRootFragment extends Fragment {
    private static final String KEY_TAB_POSITION = "tab_position";

    public static YourRootFragment newInstance(int tabPosition) {
        YourRootFragment fragment = new YourRootFragment();
        Bundle args = new Bundle();
        args.putInt(KEY_TAB_POSITION, tabPosition);
        fragment.setArguments(args);
        return fragment;
    }

    public int getTabPosition() {
        return getArguments().getInt(KEY_TAB_POSITION);
    }

    // Rest of your Fragment code...
}

Then update your Activity's onCreate method to sync these restored Fragments:

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.your_activity_layout);

    MyViewPagerAdapter adapter = new MyViewPagerAdapter(getSupportFragmentManager());
    ViewPager viewPager = findViewById(R.id.view_pager);
    viewPager.setAdapter(adapter);

    // If we're restoring from a saved state, sync existing Fragments to the adapter
    if (savedInstanceState != null) {
        List<Fragment> restoredFragments = getSupportFragmentManager().getFragments();
        if (restoredFragments != null) {
            for (Fragment fragment : restoredFragments) {
                if (fragment instanceof YourRootFragment) {
                    int tabPosition = ((YourRootFragment) fragment).getTabPosition();
                    adapter.registerFragment(tabPosition, fragment);
                }
            }
        }
    }
}

3. Always Use Registered Fragments for Stack Operations #

Whenever you need to add a new Fragment (like A2 on top of A1) to a tab's stack, never call getItem directly—use the registered instance from the adapter instead. This ensures you're working with the same Fragment instance that the system restored:

// Get the root Fragment for the current tab
Fragment currentRootFragment = adapter.getRegisteredFragment(currentTabPosition);
if (currentRootFragment != null) {
    // Perform your fragment transaction to add A2
    FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();
    transaction.replace(R.id.tab_fragment_container, new A2Fragment());
    transaction.addToBackStack(null);
    transaction.commit();
}

Why This Works #

By keeping your registeredFragments array in sync with the FragmentManager's actual instances, you avoid creating duplicate Fragments during recreation. The system handles restoring the existing Fragment stack, and your adapter just needs to reference those restored instances instead of creating new ones.

内容的提问来源于stack exchange，提问作者nicolas asinovich