Please check my answer here. Basically I just had to :
@Override
protected void onSaveInstanceState(Bundle outState) {
//No call for super(). Bug on API Level > 11.
}
I just do not make the call to
.super()
and everything works great. I hope this will save you some time.
EDIT: after some more research, this is a known bug in the support package.
If you need to save the instance, and add something to your
outState
Bundle
you can use the following :@Override
protected void onSaveInstanceState(Bundle outState) {
outState.putString("WORKAROUND_FOR_BUG_117_KEY", "WORKAROUND_FOR_BUG_117_VALUE");
super.onSaveInstanceState(outState);
}
EDIT2: this may also occur if you are trying to perform a transaction after your
Activity
is gone in background. To avoid this you should use commitAllowingStateLoss()
EDIT3: The above solutions were fixing issues in the early support.v4 libraries from what I can remember. But if you still have issues with this you MUST also read @AlexLockwood 's blog : Fragment Transactions & Activity State Loss
Summary from the blog post (but I strongly recommend you to read it) :
- NEVER
commit()
transactions afteronPause()
on pre-Honeycomb, andonStop()
on post-Honeycomb - Be careful when committing transactions inside
Activity
lifecycle methods. UseonCreate()
,onResumeFragments()
andonPostResume()
- Avoid performing transactions inside asynchronous callback methods
- Use
commitAllowingStateLoss()
only as a last resort
No comments:
Post a Comment