ViewPager does not redraw content, remains/turns blank
If the ViewPager
is set inside a Fragment with a FragmentPagerAdapter
, use getChildFragmentManager()
instead of getSupportFragmentManager()
as the parameter to initialize your FragmentPagerAdapter
.
mAdapter = new MyFragmentPagerAdapter(getChildFragmentManager());
Instead of
mAdapter = new MyFragmentPagerAdapter(getSupportFragmentManager());
I had the exact same problem but I actually destroyed the view in destroyItem (I thought). The problem however was that I destroyed it using viewPager.removeViewAt(index);
insted of viewPager.removeView((View) object);
Wrong:
@Override
public void destroyItem(ViewGroup viewPager, int position, Object object) {
viewPager.removeViewAt(position);
}
Right:
@Override
public void destroyItem(ViewGroup viewPager, int position, Object object) {
viewPager.removeView((View) object);
}
We finally managed to find a solution. Apparently our implementation suffered of two issues:
- our adapter did not remove the view in
destroyItem()
. - we were caching views so that we'd have to inflate our layout just once, and, since we were not removing the view in
destroyItem()
, we were not adding it ininstantiateItem()
but just returning the cached view corresponding to the current position.
I haven't looked too deeply in the source code of the ViewPager
- and it's not exactly explicit that you have to do that - but the docs says :
destroyItem()
Remove a page for the given position. The adapter is responsible for removing the view from its container, although it only must ensure this is done by the time it returns from finishUpdate(ViewGroup).
and:
A very simple PagerAdapter may choose to use the page Views themselves as key objects, returning them from instantiateItem(ViewGroup, int) after creation and adding them to the parent ViewGroup. A matching destroyItem(ViewGroup, int, Object) implementation would remove the View from the parent ViewGroup and isViewFromObject(View, Object) could be implemented as return view == object;.
So my conclusion is that ViewPager
relies on its underlying adapter to explicitly add/remove its children in instantiateItem()
/destroyItem()
. That is, if your adapter is a subclass of PagerAdapter
, your subclass must implement this logic.
Side note: be aware of this if you use lists inside ViewPager
.