IssueTracker

Hi all, I've implemented custom navigator to provide with Navigation Shared Elements transition ability https://github.com/lion4ik/aac-navigation-shared-elements-transition

Is there any info if it's planned to be implemented?

Support for shared elements for both activities and fragments has been added in https://android-review.googlesource.com/c/platform/frameworks/support/+/752138 through the introduction of a general purpose Navigator.Extras interface, providing a way to send a specific Navigator extra information at runtime (such as the Views you want included in shared element transitions).

This means for activity destinations, you can now provide any ActivityOptionsCompat instance you want alongside your navigate() call. For fragment destinations, you provide a map of shared elements. Documentation will be provided for both of these use cases.

This will be available in 1.0.0-alpha06.

Yes, it's worked in 1.0.0-alpha06, but only in forward direction...

Component used: Navigation
Version used: 1.0.0-alpha06
Devices/Android versions reproduced on: All

Fragment one: RecyclerView (GridLayoutManager). Transition name to ImageView is assigned in Adapter from model's name (unique)
Fragment two: Detail Fragment with ImageView and some text data. Transition name retrieved from argument's bundle.

Forward shared transition works excellent, but when I press "back" button there is no transition at all.
In NavHostActivity: override fun onSupportNavigateUp() = findNavController(R.id.nav_host_fragment).navigateUp()

In old paradigm

fragmentManager
            .beginTransaction()
            .addSharedElement(sharedImageView, transitionName)
all worked fine.

https://issuetracker.google.com/issues/116250233 has an example of Shared Element transitions that works in both directions, so this is likely due to the edge cases of shared element transitions and not something caused by navigation. Please open a new issue with a sample project if you're still running into issues.

https://android-review.googlesource.com/846338 adds a setFallbackOnNavigateUpListener method on AppBarConfiguration that allows you to register an OnNavigateUpListener to handle cases where navController.navigateUp() return false.

This allows you to call onSupportNavigateUp() (or super.onSupportNavigateUp() if you're using an ActionBar) from that method to have your Up button transition between activities.

This will be available in 1.0.0-alpha09.

There is Jarks when implementing this way to navigate up between activities.