The Animate transitions between destinations documentation details the four types of animations: Entering a destination Exiting a destination Entering a destination via a pop action Exiting a destination via a pop action “Entering” refers to the destination that is coming onto the screen, while “exiting” refers to the destination leaving the screen. Therefore when you … Read more
The navigation graph only exists within a single activity. As per the Migrate to Navigation guide, <activity> destinations can be used to start an Activity from within the navigation graph, but once that second activity is started, it is totally separate from the original navigation graph (it could have its own graph or just be … Read more
R.anim has the default animations defined (as final): nav_default_enter_anim nav_default_exit_anim nav_default_pop_enter_anim nav_default_pop_exit_anim in order to change this behavior, you would have to use custom NavOptions, because this is where those animation are being assigned to a NavAction. one can assign these with the NavOptions.Builder: protected NavOptions getNavOptions() { NavOptions navOptions = new NavOptions.Builder() .setEnterAnim(R.anim.default_enter_anim) .setExitAnim(R.anim.default_exit_anim) … Read more
It’s actually because of: android:label=”fragment_main” Which you have set in the xml. So what is the proper way to show the title for Fragments using Navigation Component? setTitle() works at this point. But, because you set label for those Fragments, it might show the label again when recreating the Activity. The solution will probably be … Read more
Reference to the displayed fragment (AndroidX): java public Fragment getForegroundFragment(){ Fragment navHostFragment = getSupportFragmentManager().findFragmentById(R.id.nav_host_fragment); return navHostFragment == null ? null : navHostFragment.getChildFragmentManager().getFragments().get(0); } kotlin val navHostFragment: Fragment? = supportFragmentManager.findFragmentById(R.id.nav_host_fragment) navHostFragment?.childFragmentManager?.fragments?.get(0) Here nav_host_fragment is an ID of the fragment tag in your activity_main.xml with android:name=”androidx.navigation.fragment.NavHostFragment”
In the 1.3.0-alpha04 version of AndroidX Fragment library they introduced new APIs that allow passing data between Fragments. Added support for passing results between two Fragments via new APIs on FragmentManager. This works for hierarchy fragments (parent/child), DialogFragments, and fragments in Navigation and ensures that results are only sent to your Fragment while it is … Read more
This is more a heads up than an answer. But I hope it helps. Summary: (As others have already said:) Successive calls to Navigation functions are the reason of most of these exceptions. Given how the android components are structured, specially how MediatorLiveData works, people may sometimes want to join data nodes in a single … Read more
You should click on “text” tab in navigation editor (xml file of the navigation graph), and add: tools:layout=”@layout/layout_name” inside destination element. Should be something like this: <fragment android:id=”@+id/someFragment” android:name=”com.freesoulapps.navigationtest.fragments.SomeFragment” android:label=”Some Fragment” tools:layout=”@layout/layout_name”> </fragment>
May 2019 Update: DialogFragment are now fully supported starting from Navigation 2.1.0, you can read more here and here Old Answer for Navigation <= 2.1.0-alpha02: I proceeded in this way: 1) Update Navigation library at least to version 2.1.0-alpha01 and copy both files of this modified gist in your project. 2) Then in your navigation … Read more
To add androidx.navigation.safeargsplugin follow below step’s classpath “android.arch.navigation:navigation-safe-args-gradle-plugin:1.0.0-alpha09” (latest) Add above to your Project Gradel file inside dependency block Then add apply plugin: ‘androidx.navigation.safeargs’ to your app/Module gradle file