Obsolete
Status Update
No update yet.
Comments
jb...@google.com
ap...@google.com
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
th...@outlook.com
Great! Thanks a lot, I'll look for the live updates soon!
Description
Version used: 1.8.0-SNAPSHOT
I've written a test to showcase a bug I encounter in real world usage where sometimes when navigating back using the 'navigate up' back button, the animation is not played and the top fragment remains on top. It seems to happen in combination with a shared element transition and predictive back.
Navigating back from this undefined state triggers a memory leak.
The test is available in the sample project: