IssueTracker

Seems like this is already fixed in master as a side effect of https://issuetracker.google.com/issues/145769287. Can you confirm this is fixed for you if you use the latest snapshot?

You'd want to add the snapshot repository to your repositories block:

maven {
  url "https://ci.android/com/builds/submitted/6080026/androidx_snapshot/latest/repository/"
}

then switch to androidx.fragment:fragment-ktx:1.3.0-SNAPSHOT.

We'll look into cherry picking the changes into Fragment 1.2.0

Great, thanks for confirming.

While there isn't any specific changes needed for this issue (as the issue was already fixed before this bug was filed), I do want to explain what exactly is going to happen from a release process:

First, we'll be cherry picking in the changes needed into a Fragment 1.2.0-rc05 release (it was too late to hit rc04, which already went out earlier today). Namely, these two changes:

• https://android-review.googlesource.com/1178750/
• https://android-review.googlesource.com/1183079/ (this was the fix for the bug mentioned in comment#3, FWIW)

Secondly, we've added additional testing (in an unrelated, but fortuitously timed effort) specifically to cover this case to ensure this doesn't happen again in https://android-review.googlesource.com/1193030

For the test in https://android-review.googlesource.com/1193030, isDestroyed() only exists on API 17 and higher: https://developer.android.com/reference/android/app/Activity.html#isDestroyed()

Project: platform/frameworks/support
Branch: androidx-main
Author: Marcello Galhardo <mgalhardo@google.com>
Link:      https://android-review.googlesource.com/3337893

Fix SavedStateReadWriteProperty saving outdated values

Fix `SavedStateReadWriteProperty` saving outdated values 
 
* `value` was incorrectly resolving to the initial value instead of the updated `this.value`. 
* Includes a fix in the unit test to catch this problem if it ever happens again. 
 
Test: SavedStateRegistryOwnerDelegatesTest 
Bug: 376027806 
Change-Id: I48469094b4064964b4800684c0702bfc99b3b2a5

This has been fixed internally and will be available in SavedState 1.3.0-alpha05.

Project: platform/frameworks/support
Branch: androidx-main
Author: Kuan-Ying Chou <kuanyingchou@google.com>
Link:      https://android-review.googlesource.com/3342882

Fix empty SavedStates not getting restored

Fix empty SavedStates not getting restored 
 
Fixes an issue that when we restore an empty SavedState (e.g. from an empty List or an object without properties) we will ignore it and call the initailizer instead. 
 
Bug: 376027806 
Bug: 376026744 
Test: SerializationTest.kt, SavedStateRegistryOwnerDelegatesTest.kt 
Change-Id: Ibc7b93a58c3327589e1b1e30573459dde266ae72

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-viewmodel-savedstate:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-android:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-desktop:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iosarm64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iossimulatorarm64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iosx64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-linuxarm64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-linuxx64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-macosarm64:2.9.0-alpha07
• androidx.lifecycle:lifecycle-viewmodel-savedstate-macosx64:2.9.0-alpha07
• androidx.savedstate:savedstate:1.3.0-alpha05
• androidx.savedstate:savedstate-android:1.3.0-alpha05
• androidx.savedstate:savedstate-desktop:1.3.0-alpha05
• androidx.savedstate:savedstate-iosarm64:1.3.0-alpha05
• androidx.savedstate:savedstate-iossimulatorarm64:1.3.0-alpha05
• androidx.savedstate:savedstate-iosx64:1.3.0-alpha05
• androidx.savedstate:savedstate-linuxarm64:1.3.0-alpha05
• androidx.savedstate:savedstate-linuxx64:1.3.0-alpha05
• androidx.savedstate:savedstate-macosarm64:1.3.0-alpha05
• androidx.savedstate:savedstate-macosx64:1.3.0-alpha05

Project: platform/frameworks/support
Branch: androidx-main
Author: Kuan-Ying Chou <kuanyingchou@google.com>
Link:      https://android-review.googlesource.com/3343740

Don't load value from SavedState or call init() when set() happens before get()

Don't load value from SavedState or call init() when set() happens before get() 
 
Bug: 376027806 
Bug: 376026744 
Test: SerializationTest, SavedStateRegistryOwnerDelegatesTest 
Change-Id: I466a149716350aa5a4a8b50d787c14143b3a4060

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.lifecycle:lifecycle-viewmodel-savedstate:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-android:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-desktop:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iosarm64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iossimulatorarm64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-iosx64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-linuxarm64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-linuxx64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-macosarm64:2.9.0-alpha08
• androidx.lifecycle:lifecycle-viewmodel-savedstate-macosx64:2.9.0-alpha08
• androidx.savedstate:savedstate:1.3.0-alpha06
• androidx.savedstate:savedstate-android:1.3.0-alpha06
• androidx.savedstate:savedstate-desktop:1.3.0-alpha06
• androidx.savedstate:savedstate-iosarm64:1.3.0-alpha06
• androidx.savedstate:savedstate-iossimulatorarm64:1.3.0-alpha06
• androidx.savedstate:savedstate-iosx64:1.3.0-alpha06
• androidx.savedstate:savedstate-linuxarm64:1.3.0-alpha06
• androidx.savedstate:savedstate-linuxx64:1.3.0-alpha06
• androidx.savedstate:savedstate-macosarm64:1.3.0-alpha06
• androidx.savedstate:savedstate-macosx64:1.3.0-alpha06