Fixed
Status Update
No update yet.
Comments
sa...@google.com
Comment has been deleted.
ap...@google.com
Could you please describe how/where you changed your system to a manual setting?
sa...@google.com
sr...@gmail.com
Based on its date, this issue was originally reported before Android 2.3. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.
Description
The
FragmentManagershould be converted over to saving its state using theSavedStateRegistryarchitecture component.We should provide
FragmentManagerwith aSavedStateRegistryControllerand move all of the code from theFragmentActivity'sinit()into theattachController()method ofFragmentManager.It currently relies on the
SavedStateRegistryof theFragmentActivitywhich hacked together methods likemarkFragmentsCreated()andmFragments.saveAllState()that can likely be called directly from theFragmentManager.The more complex piece is moving the
OnContextAvailableListener()over sinceFragmentManagerdoes not have the same signal for when theContextis immediately available.