Specifying initialParams on a bottom tab screen with a nested stack navigator causes screens to reappear after being closed.

[RosesAreMerry]

Current behavior

I have a bottom tab navigator which contains two tabs, home and menu, which each contain a stack navigator to handle multiple pages. Menu contains 2 screens, catalog and search, where catalog is the initial screen. If initial params (of any kind, even an empty object) are provided, then if you navigate to search, close search, navigate away from menu, and navigate back to it, search will reappear. If you do not provide initial params, then search will not reappear. This only happens when navigating with the format navigate($tabName, {screen: $screenName}).

The behavior is shown in the repro, one tab is given initial params of {} and the other is given none. One will save the screen, the other will not.

Expected behavior

I expect the tab navigator to not regenerate a closed tab when inital params are provided.

Reproduction

https://snack.expo.dev/M574fTBn08bklhl6cV_qb

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• @react-navigation/native-stack
• react-native-tab-view

Environment

• [] I've removed the packages that I don't use

package	version
@react-navigation/native	^6.0.8
@react-navigation/bottom-tabs	^6.0.9
@react-navigation/native-stack	^6.7.0
react-native-safe-area-context	^4.4.1
react-native-screens	^3.19.0
react-native	^0.71.7
node	20.15.1
yarn	1.22.22

[github-actions]

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• @react-navigation/native (found: 6.0.8, latest: 6.1.18)
• @react-navigation/bottom-tabs (found: 6.0.9, latest: 6.6.1)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[RosesAreMerry]

typing the newest versions into the reproduction shows the error still ocurring on these versions.

[abdi4]

+1

[jsellam]

I have a similar issue, but with deep linking.
To use your example, if the app is already opened in a screen and I trigger a deeplink with npx uri-scheme open to the search screen I have the same issue.
but in my example I never use screen params, and it work well if the app is killed before the deeplink trigger.

thx, Jeremie.

[jsellam]

This is the routes log from my app, just after the deeplink trigger :

   "routes": [
                {
                  "key": "profileScreen-RHVXW0xlMmd4Aocq96GWM",
                  "name": "profileScreen"
                },
                {
                  "key": "appSettingsScreen-qAjYwnrUmQqOeAVMbaTUS",
                  "name": "appSettingsScreen",
                  "path": "profile/settings"
                }
              ]

and when I go to the "home tab" :

"routes": [
  {
    "name": "homeScreen",
    "key": "homeScreen-cGfuptkwxD-2BTFmAYUBd"
  },
  {
    "name": "learningStack",
    "key": "learningStack-HDS_xgWJeJL4DRZJz7u8C"
  },
  {
    "name": "walletStack",
    "key": "walletStack-FIUdM-HgSdDv4rALP1fcy"
  },
  {
    "name": "profileStack",
    "key": "profileStack-tiHKXKf1zrViIxX8Kkgf6",
    "params": {
      "initial": false,
      "screen": "appSettingsScreen",
      "path": "profile/settings"
    }
  }
]

some params are added to the settings screen, and this screen stay in the stack when I click on the profile tab.

My packages versions :

 "@react-navigation/bottom-tabs": "^6.6.1",
  "@react-navigation/native": "^6.1.18",
    "@react-navigation/native-stack": "^6.11.0",
    "@react-navigation/stack": "^6.4.1",