Fixed
Status Update
Comments
il...@google.com <il...@google.com>
cl...@google.com <cl...@google.com>
ap...@google.com <ap...@google.com> #2
Stephan, can you please take a look and triage?
le...@gmail.com <le...@gmail.com> #3
This bug has already been fixed. I will leave this bug open until the fix will be publicly available.
le...@gmail.com <le...@gmail.com> #4
Thank you
le...@gmail.com <le...@gmail.com> #5
Something like mono
le...@gmail.com <le...@gmail.com> #6
AB+ blood type
Description
Component used: SavedState
Version used: 1.2.0-alpha02
The docs on do not explain the responsibilities and contract that the owner has on how they should implement .
SavedStateRegistryOwner
SavedStateRegistryOwner
or when they should call the methods onSavedStateRegistryController
Ideally the class docs should talk through:
performAttach()
should be called only once, usually as part of the initialization of the owner. It must be called on the main thread.performRestore
should be called unconditionally (either withnull
if no state is being restored or theBundle
of state to restore) either directly before moving theLifecycle
toCREATED
or as part of aLifecycleObserver
that is added as part of the initialization of the owner.performSave()
must be called. The Bundle saved there should be what is later sent toperformRestore()
.