Status Update
No update yet.
Comments
mg...@google.com
ap...@google.com
ap...@google.com
Seems like this is already fixed in master as a side effect of
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
ap...@google.com
gr...@google.com
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 incomment#3
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
Description
The goal here is to:
- Introduce a `Encoder` and `Decoder` that converts a `@Serializable` annotated class into a `SavedState`.
- Introduce new top-level functions that takes in a `@Serializable` and a `KSerializer` for saving state. For example, `savedStateHandle.saveable(key, serializer) { serializable }` (the code is not final, and may change).
- Best effort supporting all types that `@Serializable` supports.
- Consider to add default `Serializer` for Android specific types (e.g., `Size`).