Fix wrong goUp behavior after migration

Author: staszekscp

src/CONST/index.ts

@@ -5230,6 +5230,7 @@ const CONST = {
             REPLACE: 'REPLACE',
             PUSH: 'PUSH',
             NAVIGATE: 'NAVIGATE',
+            NAVIGATE_DEPRECATED: 'NAVIGATE_DEPRECATED',
             SET_PARAMS: 'SET_PARAMS',
 
             /** These action types are custom for RootNavigator */

src/libs/Navigation/Navigation.ts

@@ -305,6 +305,15 @@ function goUp(backToRoute: Route, options?: GoBackOptions) {
         return;
     }
 
+     /**
+     * In react-navigation 7 the behavior of the `navigate` function has slightly changed.
+     * If it detects that a screen that we want to navigate to is already in the stack, it doesn't go back anymore.
+     * More: https://reactnavigation.org/docs/upgrading-from-6.x#the-navigate-method-no-longer-goes-back-use-popto-instead
+     */
+    if (minimalAction.type === CONST.NAVIGATION.ACTION_TYPE.NAVIGATE) {
+        minimalAction.type = CONST.NAVIGATION.ACTION_TYPE.NAVIGATE_DEPRECATED
+    }
+
     const indexOfBackToRoute = targetState.routes.findLastIndex((route) => doesRouteMatchToMinimalActionPayload(route, minimalAction, compareParams));
     const distanceToPop = targetState.routes.length - indexOfBackToRoute - 1;