I’m using navigation component ‘androidx.navigation:navigation-fragment-ktx:2.3.3’ ‘androidx.navigation:navigation-ui-ktx:2.3.3′ I don’t understand why when I’m navigating from my startDestination to the next Fragment I get a short blinking and I see the previous activity for a couple of millisec. This doesn’t happen when I’m navigating to different fragments. This happens with and without the navigation animations. Tried with ..
I am having 4 fragments in Navigation Graph, Named A, B, C, D, On which i am getting some data from the user. When i an in a normal flow (A->B->C->D) and press back button everything(back-stack) working fine. But i have a case in which i have and edit information flow, Suppose user left the ..
Good day. So I’ve been working around with NavComponent of Jetpack for Android I’ve thought that management of BackStack of fragments had to be implemented there already, well in fact it is there but I have faced an issue. Here is my structure: I have and entry Activity I have a NavHost in the activity ..
Please, I integrated the new Navigation Controller Component, using navHostFragment. My project runs on one activity-to-many fragments. It got a drawer & toolbar. I read that it is possible to set the ids in both menus (drawer, toolbar), to same ids in nav_graph for navigation when onClick event occurs. activity_main.xml <androidx.drawerlayout.widget.DrawerLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" android:layout_width="match_parent" android:layout_height="match_parent" ..
My application has 4 screens: Login, Home, Profile, Settings. Login is the start screen. Then there is the Main screen where the BottomNavigationView switches 3 other screens. I made 2 navigation graphs: the first for the Login-Main fragments, the second for the Home-Profile-Settings fragments. The second graph was attached to the BottomNavigationView. And it works ..
In my app im able to open two fragments by clicking 2 different menu items in the toolBar like in this code: override fun onOptionsItemSelected(item: MenuItem): Boolean { when (item.itemId) { R.id.action_signout -> { FirebaseAuth.getInstance().signOut() return true } R.id.search -> { navController.navigate(R.id.nav_service_search) if (fragmentManager.findFragmentById(R.id.userInfoFragment) != null) { navController.popBackStack(R.id.userInfoFragment, false) } return true } R.id.user_account -> ..
In my app I use NavController with Fragments. In some fragments I need to access views on MainActivity layout. I do that in this way: val fab: FloatingActionButton = requireActivity().findViewById(R.id.fab) This works properly as expected. However, one view does not want to be called and the findViewById() returns null. The layout structure is like this. ..
In my app I have one Activity and the rest are fragments. Right now I am trying to get run as follows: Let’s say, I have Fragments A (Home), B, and C. The scenario is this: I navigate from A to B that shows me some data that I pass from A by Safe args. ..
Let me explain the whole thing, just in case. I’m using BottomNavigationView with Jetpack’s Mobile Navigation graphs and so. I reimplemented the method: NavigationUI.setupWithNavController(…) during navigation setup, instead of using this method I made a very similar: customSetupWithNavController(…) the only changes I made was to change de default fading transition between fragments, and started to ..
I am facing the following problem. I have one Activity with four Fragments. Three of them are in DrawerLayout as Items. Around those three Fragments everything works fine. However, when I change to the last one, let’s say TestFragment, that is not in DrawerLayout, by using navController.navigate(R.id.nav_test), and then come back to the HomeFragment by ..
Recent Comments