Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
I've just tried a simple workaround whereby I return the types contained within the library inside an object via a bootstrap call. That doesn't work - no error message but the debugger drops out when stepping over code that references the types.
ap...@google.com
Please share a spreadsheet that shows what you'd like to be able to do with libraries. You can share it with me at jkleinert AT google.com
il...@google.com
I've just shared a couple of spreadsheets with you.
Description
Component used: Lifecycle
Version used: 2.5.0-alpha01
Currently the call to
enableSavedStateHandles()creates aViewModelusing theViewModelStore. This requires that the ViewModelStore be set on any component attempting to make the call, but there are scenarios where the call toenableSavedStateHandlesneeds to happen before that in particular in the Fragment and Navigation components where the call is not immediately made when the object is constructed or sometimes not at all.If we remove the reliance on
SavedStateHandles(and therefore view models), we can lean into theSavedStateProviderAPIs and the call toenableSavedStateHandles()can be made before theViewModelStoreis set.