Solution: In Fragmentactivity OnCreate method to judge Savedinstancestate==null to generate a new fragment;
@Override public void OnCreate (Bundle savedinstancestate) {if (savedinstancestate! = null) {Savedin Stancestate.putparcelable ("android:support:fragments", null); } super.oncreate (Savedinstancestate); Context = (baseactivity) getactivity (); }
Cause: If the system is out of memory, or switching the screen, or the app is running in the background for a long time, the activity may be reclaimed by the system, and then fragment will not be recycled as the activity is recycled, resulting in Fragment loses the corresponding activity.
Here, suppose we inherit from the Fragmentactivity class as Mainactivity, which uses the fragment as Fragmenta.
The app changes: For some reason, the system recycle Mainactivity--fragmenta is not recycled--click the app again--the first thing that's loaded is the Fragmenta page that's not recycled--because mainactivity is recycled, The system restarts Mainactivity,fragmenta will also be loaded again-the page is cluttered because a layer of fragmenta is overlaid on it-(if Fragmenta uses the Getactivity () method) to report a null pointer, Appears crash.
The system saves the fragment object through Fragmentactivity call Onsaveinstancestate, when the system restores the saved fragment, but when fragmentactivity re-executes the life cycle, We re-generated the fragment object attached to the fragmentactivity, the system resumed fragment and the Activity Lost Association, error;
Therefore, in the Fragmentactivity OnCreate method to judge Savedinstancestate==null to generate a new fragment;
Use the Fragment app to place the background for a long time again into the solution of the Flash back