Causes issues in the following scenario:
- On first screen there is an AdapterList component with
FROM element.
- User navigates to next screen, that has no
SharedElement.
- User navigates to next screen that has a
TO element.
Here the transition between FROM and TO would start because we still remember that FROM element from first screen. This is due to a bug in Compose that cause AdapterList to never invoke onDispose on list items, so FROM element would never know it disappeared.
https://issuetracker.google.com/issues/150174792
I'm not sure if any workaround can be implemented before it's fixed.