1

I’m running into an issue with navigation, while using backBehavior="fullHistory". Navigation tree

- (tabs)
  |- agenda
  |   `- appointment
  `- clients
      `- client

Flow: (tabs) ➡️ agenda ➡️ appointment (1) ➡️ client (A)

Expected back behavior: client (A) ➡️ appointment (1) ➡️ agenda

Current behavior: With router.push + anchor={true}: client (A) ➡️ clients 🛑 (skips appointment)

Without anchor: No back button is shown on client (A) — so it’s not possible to go back to appointment (1).

Summary: Navigating deeper than one level in tabs breaks expected back navigation. I’d expect client (A) to always have a back button pointing to appointment (1).

Question: How can I achieve the expected navigation from appointment (1) to client (A)?

expo-env-info 2.0.7 environment info:
   System:
     OS: Windows 11 10.0.26100
   Binaries:
     Node: 22.12.0 - ~\AppData\Local\nvs\default\node.EXE
     npm: 10.9.0 - ~\AppData\Local\nvs\default\npm.CMD
   IDEs:
     Android Studio: AI-243.25659.59.2432.13423653
   npmPackages:
     expo: ^53.0.22 => 53.0.22 
     expo-router: ~5.1.5 => 5.1.5 
     react: 19.0.0 => 19.0.0 
     react-dom: 19.0.0 => 19.0.0 
     react-native: 0.79.5 => 0.79.5 
   Expo Workflow: bare
Improve this question
Related questions
0
expo closes when i use Alert.alert()
122
Disable back button in react navigation
0
Expo push token is not being created in android standalone app
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.