IssueTracker

It could easy to reproduce when turning on "Don't keep activities".

Project: platform/frameworks/support
Branch: androidx-master-dev

commit ba0c19707915ff87d9cac2089fcd166bb5cca17d
Author: Ian Lake <ilake@google.com>
Date:   Wed Nov 14 16:20:28 2018

    Set the correct FragmentManager on active Fragments
   
    All active Fragments should have the correct
    FragmentManager set instead of always using the
    Activity's FragmentManager.
   
    While added Fragments have their FragmentManager
    set correctly in moveToState(), active Fragments
    weren't being set correctly, causing issues when
    attempting to save the state of the FragmentManager.
   
    Test: new FragmentLifecycleTest
    BUG: 119256498
    Change-Id: I830f729d93f00859509a0844fae19752342e6ccc

M       fragment/src/androidTest/java/androidx/fragment/app/FragmentLifecycleTest.java
M       fragment/src/main/java/androidx/fragment/app/FragmentManagerImpl.java
M       fragment/src/main/java/androidx/fragment/app/FragmentState.java

https://android-review.googlesource.com/826954
https://goto.google.com/android-sha1/ba0c19707915ff87d9cac2089fcd166bb5cca17d

Thanks Ian! Looking forward to a new alpha release ASAP rather than monthly release.😅

Thanks for fixing this!

Wondering is there any release plan?

Fragments 1.1.0-alpha02 is out now with this fix.

Does Preferences also depend on Fragments?  In which case when will that be updated to 1.1.0-alpha02?  Or is the recommended practice to specify both Preferences and Fragments in build.gradle so that we can force Fragments 1.1.0-alpha02?

Re #8 - yes, if you need a specific version of Fragments, you should specify both Preferences and Fragments in your build.gradle.

The release schedule of AndroidX components is completely independent of one another, so Preferences will only get a new version when there's something new to release in Preferences.

So, in general it sounds like if an androidx dependency (such as preference) is added to build.gradle, then any dependencies of that (e.g. fragment) should also be explicitly added so that the specific version can be specified. Is that right?

In other words, when we explicitly include preference-1.1.0-alpha01 we need to be aware that the fragment-alpha1.1.0-alpha01 is automatically being brought in and so might affect the fragment behaviour.  Sorry, I know this is rather OT.

Thanks, fix confirmed

alpha02 version of fragments didn't fix this for me. Is there another solution?