Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Status is still Assigned, but Compose 1.1.0 was already released. Did the ETA change for this feature?
jb...@google.com <jb...@google.com> #3
The Compose Animation APIs Navigation needs (such as AnimatedContent
) are still @Experimental
in Compose 1.1.0.
ju...@google.com <ju...@google.com> #4
Update: Same case for Compose 1.2.0
Description
The reason for this is that if a fragment on the back stack is destroyed while it is still created, we ensure the entry makes it to destroyed, but failed to clear some associated state. The state remains around and prevents us from popping the Nav back stack during system back.