diff --git a/src/components/Navigation/TopLevelNavigationTabBar/getIsScreenWithNavigationTabBarFocused.ts b/src/components/Navigation/TopLevelNavigationTabBar/getIsScreenWithNavigationTabBarFocused.ts
index a7508da770d8..fca01eb67add 100644
--- a/src/components/Navigation/TopLevelNavigationTabBar/getIsScreenWithNavigationTabBarFocused.ts
+++ b/src/components/Navigation/TopLevelNavigationTabBar/getIsScreenWithNavigationTabBarFocused.ts
@@ -1,6 +1,5 @@
 import {findFocusedRoute} from '@react-navigation/native';
 import type {NavigationState} from '@react-navigation/native';
-import {isSplitNavigatorName} from '@libs/Navigation/helpers/isNavigatorName';
 import SCREENS_WITH_NAVIGATION_TAB_BAR from './SCREENS_WITH_NAVIGATION_TAB_BAR';
 
 function getIsScreenWithNavigationTabBarFocused(state: NavigationState) {
@@ -9,7 +8,7 @@ function getIsScreenWithNavigationTabBarFocused(state: NavigationState) {
     const routeName = focusedRoute?.params && 'screen' in focusedRoute.params ? (focusedRoute.params.screen as string) : focusedRoute?.name;
     // We are checking if the focused route is a split navigator because there may be a brief moment where the navigator doesn't have state yet.
     // That mens we don't have screen with bottom tab focused. This caused glitching.
-    return SCREENS_WITH_NAVIGATION_TAB_BAR.includes(routeName ?? '') || isSplitNavigatorName(routeName);
+    return SCREENS_WITH_NAVIGATION_TAB_BAR.includes(routeName ?? '');
 }
 
 export default getIsScreenWithNavigationTabBarFocused;