Navigation state is properly managed at the root

Without root-level state tracking, analytics firing on screen changes, auth-gated redirects, and deep-link-driven UI toggles all become per-screen boilerplate that drifts out of sync. Missing onStateChange means you cannot detect when a user lands on a sensitive screen to refresh a token, or log funnel events centrally. The app ends up with duplicated tracking code and screens that never tell the rest of the app where the user is.

Attach an onStateChange handler to NavigationContainer so analytics and global reactions fire in one place. Keep the latest state in a ref or store so any screen can read it:

<NavigationContainer
  linking={linking}
  onStateChange={(state) => {
    const route = state?.routes[state.index]
    analytics.track('screen_view', { name: route?.name })
  }}
>
  <RootNavigator />
</NavigationContainer>

Put the handler in src/navigation/index.tsx so it ships with the container.