79251786

Date: 2024-12-04 15:30:15
Score: 1
Natty:
Report link

what you've done won't work because when going to C in graph 2 you won't naturally have access to the children of C from graph 1 (D or E). I would either:

  1. Just have 1 graph
  2. Navigate from G to nav graph 1 (with a "subScreen" arg) and set up redirect logic in the start of graph 1 (frag A uses arg from onCreate()) to facilitate automatic redirection - this approach can be useful in general for handling deep links. Note you will probably want "popUpTo" nav graph 1 as you navigate from A to C (you could parameterize that too if you prefer to preserve the stack when deeplinking)

Something else to bear in mind is that nav graphs can't contain each other as includes (you'll get a circular inflation error when building the app). In general look to include necessary sub graphs at the main/tab level nav graph and then you can navigate to them in downstream graphs without "including" again.

Reasons:
  • Long answer (-0.5):
  • No code block (0.5):
  • Starts with a question (0.5): what you
  • Low reputation (0.5):
Posted by: hmac