How to Determine When a Fragment Becomes Visible in ViewPager

How to Determine When a Fragment Becomes Visible in ViewPager

6 June 2024 Stephan Petzl Leave a comment Tech-Help

Managing fragment visibility within a ViewPager can be somewhat challenging, especially when dealing with events that should only trigger when a fragment is truly visible to the user. This article will help you understand how to accurately determine when a fragment becomes visible in ViewPager and provide practical solutions to implement this functionality.

Problem Statement

When using ViewPager with FragmentPagerAdapter, the onResume() method of a fragment is called before it becomes visible. This occurs because ViewPager preloads adjacent fragments for smoother transitions. For example, if you have two fragments and the second one requires user authentication, you need to prompt for login when the second fragment becomes visible, not when it is preloaded.

Solution: Overriding setUserVisibleHint

The most effective way to detect the visibility of a fragment in ViewPager is by overriding the setUserVisibleHint method. This method is called when the fragment’s visibility to the user changes. Here’s how you can implement it:

public class MyFragment extends Fragment {
    public void setUserVisibleHint(boolean isVisibleToUser) {
        if (isVisibleToUser) {
            // Fragment is visible
        } else {
            // Fragment is not visible

Considerations and Updates

With the Android Support Library (rev 11) and newer versions, setUserVisibleHint and getUserVisibleHint work as expected. However, be cautious as the default value of getUserVisibleHint() is true, which might cause issues if not handled properly. To ensure correct behavior, you can initialize it in the onCreate method:

public void onCreate(@Nullable Bundle savedInstanceState) {

Alternative Methods

In some cases, using onPageChangeListener can also be effective. Here’s a brief example:

ViewPager pager = (ViewPager) findViewById(;
FragmentPagerAdapter adapter = new FragmentPagerAdapter(getFragmentManager());
pager.addOnPageChangeListener(new ViewPager.OnPageChangeListener() {
    public void onPageSelected(int position) {

    public void onPageScrolled(int position, float positionOffset, int positionOffsetPixels) {}

    public void onPageScrollStateChanged(int state) {}

ViewPager2 and Newer Implementations

For ViewPager2 or ViewPager with androidx.fragment:fragment:1.1.0 and newer, the visibility can be managed using onResume and onPause callbacks. This can be enabled by passing FragmentPagerAdapter.BEHAVIOR_RESUME_ONLY_CURRENT_FRAGMENT as a parameter:

FragmentPagerAdapter(fragmentManager, BEHAVIOR_RESUME_ONLY_CURRENT_FRAGMENT);

For more details on advanced configurations and testing techniques, refer to our documentation on advanced configuration.


Implementing these methods will help ensure that your fragments within a ViewPager are handled correctly, triggering events only when they are truly visible to the user. This is particularly useful for scenarios requiring user interactions like authentication prompts.

For mobile developers, managing fragment visibility efficiently can save considerable time and effort. If you’re looking for a solution that further simplifies your development process, consider using Repeato. Repeato is a no-code test automation tool for iOS and Android that allows you to create, run, and maintain automated tests rapidly. It employs computer vision and AI, enabling even non-technical team members to handle test automation, allowing developers to focus on building a great product.

Like this article? there’s more where that came from!