SOLID POD: Fail to navigate to the specified widget

[cdawei]

There are more than one scenarios where the navigator does not redirect to the specified child widget, e.g. two issues captured by

• https://github.com/anusii/keypod/issues/72
• https://github.com/anusii/solidpod/issues/149

Although a workaround that seemed to work is using Navigator.push instead of Navigator.pushReplacement for the widget in question, but there are a few problems for this workaround:

1. It needs to be done for each case in keypod (a user of solidpod) which really should not worry about an issue like this.
2. It seems unclear why using Navigator.push worked

There is likely a hidden issue in the solidpod that is the root cause, so understanding it and systematically resolve it in solidpod is preferred.

[cdawei]

Move Kevin's comment from https://github.com/anusii/solidpod/issues/149 to this issue for a continued discussion.

---

Navigator.push:

• This method pushes a new route onto the navigation stack.
• The current route remains in the stack, and the new route is added on top of it.
• When you navigate back, you return to the previous route.

Navigator.pushReplacement:

• This method pushes a new route onto the navigation stack and removes the current route.
• The current route is replaced by the new route, meaning it won't be in the stack anymore.
• When you navigate back, you won't return to the previous route but to the route before it.

When to Use Each

Use Navigator.push when:

• You want to add a new screen on top of the current screen.
• You expect the user to potentially navigate back to the previous screen.

Use Navigator.pushReplacement when:

• You want to replace the current screen entirely with a new screen.
• The current screen is no longer relevant, and you don't expect the user to navigate back to it.

[cdawei]

Related to the more general issue #159