Key Fixes:

• We no longer use react-native-paper's BottomNavigation, as it doesn’t work well with stack navigators. We switched to createBottomTabNavigator from react-navigation.

• We now place each stack navigator under a specific tab, and each stack navigator is a separate screen inside the BottomTabNavigator.

• Issue with react-native-paper: Issue Code Example

• Fixed with react-navigation: Working Code Example

Result:

• Now, each tab (Home, Profile) correctly uses a stack of screens.
• You can navigate within each stack (e.g., Home -> Details, Profile -> Profile Details).
• Only one NavigationContainer wraps everything, which resolves the "Another navigator is already registered" issue.