FragmentStatePagerAdapter中getItem()被调用两次致TTS重复播报问题求助

Hey there, I’ve run into this exact issue before—let’s break down what’s happening and fix it step by step.

Why does getItem() get called twice? #

The root cause is ViewPager’s default preloading behavior. By default, ViewPager loads the adjacent fragment(s) (offscreenPageLimit = 1) alongside the current one to make swiping smoother. So when your app starts up, it creates both the current fragment and the next one, triggering getItem() twice. If you’re initializing and triggering TTS directly in the fragment’s creation lifecycle (like onCreate() or onViewCreated()), that’s why you’re getting duplicate audio.

Fix 1: Trigger TTS only when the fragment is actually visible #

Instead of starting TTS when the fragment is created, wait until it’s fully visible to the user. Here are two reliable ways to do this:

Option A: Use ViewPager’s OnPageChangeListener (in MainActivity)

First, add a public method in your fragment to handle TTS triggering (keep initialization separate):

public class YourFragment extends Fragment {
    private TextToSpeech tts;

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        // Initialize TTS once per fragment instance
        tts = new TextToSpeech(getContext(), status -> {
            if (status == TextToSpeech.SUCCESS) {
                // Configure language or other settings here
            }
        });
    }

    // Public method to trigger TTS when needed
    public void startTextToSpeech(String content) {
        if (tts != null && tts.isLanguageAvailable(Locale.getDefault()) == TextToSpeech.LANG_AVAILABLE) {
            tts.speak(content, TextToSpeech.QUEUE_FLUSH, null, null);
        }
    }

    @Override
    public void onDestroy() {
        super.onDestroy();
        // Clean up TTS to avoid memory leaks
        if (tts != null) {
            tts.stop();
            tts.shutdown();
        }
    }
}

Then in your MainActivity, listen for page selection and trigger TTS only for the active fragment:

viewPager.addOnPageChangeListener(new ViewPager.OnPageChangeListener() {
    @Override
    public void onPageScrolled(int position, float positionOffset, int positionOffsetPixels) {}

    @Override
    public void onPageSelected(int position) {
        // Get the currently selected fragment instance
        YourFragment currentFragment = (YourFragment) pagerFragment.getAdapter().instantiateItem(viewPager, position);
        // Pass your target text here (replace with your actual content source)
        currentFragment.startTextToSpeech("Text you want to speak");
    }

    @Override
    public void onPageScrollStateChanged(int state) {}
});

Option B: Use setUserVisibleHint() (handle inside the fragment)

If you prefer managing visibility logic directly in the fragment, override setUserVisibleHint():

@Override
public void setUserVisibleHint(boolean isVisibleToUser) {
    super.setUserVisibleHint(isVisibleToUser);
    // Only trigger TTS if the fragment is visible AND has finished loading
    if (isVisibleToUser && isResumed()) {
        startTextToSpeech("Text you want to speak");
    }
}

Fix 2: (Optional) Adjust ViewPager’s preload limit #

If you really don’t want ViewPager to preload fragments, you can set the offscreen limit to 0—but note this might make swiping less smooth:

viewPager.setOffscreenPageLimit(0);

This will stop preloading, so getItem() will only be called when the fragment is needed. However, this isn’t recommended for most cases since it harms user experience.

Key Takeaway #

The core fix is decoupling your TTS trigger from the fragment’s creation. By only starting TTS when the fragment is actively visible to the user, you avoid duplicate calls caused by ViewPager’s preloading mechanism.

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