Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
Description
Component used: SavedState
Version used: 1.1.0
When
SavedStateRegistryis asked toperformSave, itputBundleThis means that in cases like Fragments, where the Fragment itself has a
SavedStateRegistryand the fragment's view has its ownSavedStateRegistry, the overall saved state is increased doubly so (at what seems like a cost of 0.2KB per fragment).While not a significant part of the total saved state, this can add up with deep stacks.