I had the same issue ("Fragment is no longer in the fragment manager")...
I'm not an Android super-expert but I solved this issue overriding
saveState() method in my class extending FragmentStatePagerAdapter:
@Override
public Parcelable saveState() {
// DO NOTHING
return null;
}
Hope this helps!
Bye
Il giorno giovedì 19 luglio 2012 21:30:37 UTC+2, user123 ha scritto:
>
> The documentation also says:
>
> " * <p>This version of the pager is more useful when there are a large
> number
> * of pages, working more like a list view. When pages are not visible to
> * the user, their entire fragment may be destroyed, only keeping the saved
> * state of that fragment. This allows the pager to hold on to much less
> * memory associated with each visited page as compared to
> * {@link FragmentPagerAdapter} at the cost of potentially more overhead
> when
> * switching between pages."
>
> So why it keeps crashing because it tries to access destroyed fragments,
> if it's designed with the fact in mind, that the fragments might be
> destroyed...?
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
