I am aware of the best practice of nesting the tab bar inside of of a stack navigator and placing the screens which you need hidden tabBars in inside the root stack navigator. link: https://reactnavigation.org/docs/hiding-tabbar-in-screens/
But is approach does not work when you need to .push from a screen that is outside of the bottom tab navigator to a screen thats inside of the bottom tab navigator. This essentially kicks the user out of the screen that is outside of the bottom tab navigator and then pushes the selected screen on top. Which is not the greatest UX.
Hopefully that made sense. Overall it is just such a shame that we still have this limitation that the native worlds don't. Not only would it make things easier to be able to dynamically hide the bottom tab bar in specific screens, it also just doesn't feel right to have to nest a navigator inside another to achieve something thats seems like it should be as simple as a true/false assignment.
Im not sure what causes the glitchy jump when the bottom tab bar is hidden or revealed from a specific screen but it is pretty noticeable. I wish I was experienced enough to dive in to the code and troubleshoot things but i'm simply not there yet. I hope theres a way this issue can be solved. Thank you for all the hard work!