See the following issues for a detailed description of the problem, and a workaround: https://github.com/react-navigation/react-navigation/issues/9744

In our app, we currently are trying to use deep links as much as possible to opt for a 'dumb' client. This allows us to receive navigation links from the backend and work similar to web. However, we have a couple of issues that we have workarounds for, primarily not being able to specify the type of navigation. One scenario that causes an issue: (I will use letters as screens) Open A which is a modal, A opens B, so modal closes. B opens A modal again, and A again opens B, however B is already on the stack, so it is treated as a default 'goBack', however this is not what we are looking for. We would like to push this screen again.

Documentation misses a guide for testing with react-navigation v5 I think we should add it and expose (if needed) routing primitives that work in test environments (like a fake Navigator)

It would useful for custom focus behavour. It should be implemented as imperative method.

I would really like to have better understanding of how to reset state. All existing examples are poor and don't really explain how to use this method for more complex tasks.

On tablet in portrait mode it should be awesome to have a tab bar at the bottom and a 1/3 pane left with a list container and at the right side of this pane a 2/3 pane with the detail view of the selection of the list item from the 1/3 part. On tablet in landscape mode, the tab bar should be better aligned at the left of the screen, and still having the 1/3 + 2/3 screen pane ratio. Actually, to be more clear it is a master(list) + detail layout.

There should be option to make our own custom screen container and drawer

i have used create material bottom tab navigator i want to hide the bottom tab navigator when i scroll on screen