Nested Viewpager Fragment not getting initialized

Question

I have 3 fragments part of a navigation drawer, one of which contains a viewpager. When I first load the app, the viewpager loads all the fragments. However, when I switch to another fragment using the navi-drawer and I switch back, one of the viewpager fragments is not loading. I have tried the code here and here but I'm not able to come up with a solution.

In my pageradapter code, in the switch case for different fragments; I have put a log for the position, and position 1 does not seem to be coming after the initial load of the app.

My question is, why is it that position 1 never gets called? Can someone explain it to me?

Here's my Pageradapter code:

 class PagerAdapter extends FragmentStatePagerAdapter {

static HeartRate_Fragment heartRate_fragment;
static Calorie_Fragment calorie_fragment;
static  Steps_Fragment steps_fragment;

int num;
public PagerAdapter(Context context, FragmentManager fm) {
    super(fm);

}
@Override
public Fragment getItem(int position) {
    //add new fragment here for homepage viewpager
    Log.d("position",position+"");
    switch (position) {

        case 0:
           if(calorie_fragment == null)
            calorie_fragment = new Calorie_Fragment();
           Log.d("flip",0+"");
            return calorie_fragment;

        case 1:
            if(heartRate_fragment == null)
                heartRate_fragment = new HeartRate_Fragment();
            Log.d("flip",1+"");
            return heartRate_fragment;


        case 2:
            if(steps_fragment == null)
            steps_fragment = new Steps_Fragment();
            Log.d("flip",2+"");
            return steps_fragment;


        default:
            return null;

    }

}

@Override
public int getCount() {
    return num;
}

public HeartRate_Fragment getHRFragment()
{
    return heartRate_fragment;
}
public Calorie_Fragment getCalorie_fragment()
{
    return calorie_fragment;
}
public  Steps_Fragment getSteps_fragment()
{
    return steps_fragment;
}

My homefragment already contains a viewpager. That viewpager contains 3 fragments. In that, the 2nd one is not getting initialized. The first and third are. — Richeek Dey, Jul 15 '16 at 05:40
I can see it not being initialized. Its a graph. And I dont see the graph. — Richeek Dey, Jul 15 '16 at 05:53
Ok. that fragment has graph. Can you post more code so we can get any mistake ? — Anshul Tyagi, Jul 15 '16 at 05:54
Can we make this a private conversation? Stackoverflow doesn't like it if we have a conversation through comments. I can send you my entire code through a zip. — Richeek Dey, Jul 15 '16 at 06:00
can you post some more code to get the idea where you do mistake.. — Harshad Pansuriya, Jul 15 '16 at 07:13
Your fragment which contains viewpager should called it's child fragment with getChildFragmentManager() if you not doing this you face unexpected behaviour. — Amir, Jul 15 '16 at 08:29
I tried getChildFragmentManager(), that doesn't resolve the issue. It pops up a "cannot resolve method getChildFragmentmanager()" error. — Richeek Dey, Jul 15 '16 at 09:02

Digvijay Singh · Accepted Answer · 2016-07-15T09:34:02.993

4

class PagerAdapter extends FragmentStatePagerAdapter {

static HeartRate_Fragment heartRate_fragment;
static Calorie_Fragment calorie_fragment;
static  Steps_Fragment steps_fragment;

int num;
public PagerAdapter(Context context, FragmentManager fm) {
super(fm);

}
@Override
public Fragment getItem(int position) {
  //add new fragment here for homepage viewpager
Log.d("position",position+"");
switch (position) {

    case 0:

        if(calorie_fragment == null){
        calorie_fragment = new Calorie_Fragment();
        return calorie_fragment;
        }else {
         return getCalorie_fragment(); }         

    case 1:
        if(heartRate_fragment == null){
            heartRate_fragment = new HeartRate_Fragment();
            return heartRate_fragment;}
         else{ return getHRFragment();}

    case 2:
        if(steps_fragment == null){
        steps_fragment = new Steps_Fragment();
        return steps_fragment;
        }
        else{ return getSteps_fragment();} 

    default:
        return null;

}

}

@Override
public int getCount() {
return 3;
}

 public HeartRate_Fragment getHRFragment()
  {
  return heartRate_fragment;
  }
  public Calorie_Fragment getCalorie_fragment()
  {
  return calorie_fragment;
  }
  public  Steps_Fragment getSteps_fragment()
  {
  return steps_fragment;
  }

try this make sure you are using getChildFragmentManager();

edited Jul 15 '16 at 09:34

answered Jul 15 '16 at 07:24

Digvijay Singh

623
9
26

note: default of **setOffscreenPageLimit** is 3 and you dont need to set it explicitly. – Amir Jul 15 '16 at 08:39
I can't use getChildFragmentManager(), in my homefragment code, when I call pagerAdapter = new PagerAdapter(getActivity().getChildFragmentManager(),3); it throws up cannot resolve method getChildFragmentmanager – Richeek Dey Jul 15 '16 at 09:09
@RicheekDey use pagerAdapter = new PagerAdapter(getChildFragmentManager()); like this inside your fragment – Digvijay Singh Jul 15 '16 at 09:12
Okay now nothing is coming. :/ the viewpager is blank now from the first time I load the app. – Richeek Dey Jul 15 '16 at 09:14
in get count you are returning num where you give value to this variable – Digvijay Singh Jul 15 '16 at 09:15
Yes, so? I'm saying right now the viewpager is not even loading any fragment. I'll show you, one sec – Richeek Dey Jul 15 '16 at 09:16
try this `@Override public int getCount() { return 3; }`make your get count return 3 – Digvijay Singh Jul 15 '16 at 09:18
This has worked like charm: Simply change from getActivity().getFragmentManager() to getChildFragmentmanager() – Samuel Owino Oct 21 '19 at 18:28

Nested Viewpager Fragment not getting initialized

1 Answers1