[v5] Nested navigation within TabBar and two initial screens navigating the same destination screen

[sbkl]

Hi

I have TabStack and the SharedElementStack.

I want to trigger the same navigation from two different screen from the tab stack.

The first screen works great. However, as soon as I trigger the navigation from the second screen, the navigation breaks when going back, the sharedElements function is not called anymore.

Below a snack reproducing my implementation and the issue I'm facing:

snack demo

Is it something I'm doing wrong or just because it is a prerelease for the v3 and will be fixed later on? Does that work using the latest version of this package with react navigation v4?

Thanks.

[miklschmidt]

Same issue with @react-navigation/material-top-tabs

[s-rayed]

Was anyone able to fix this issue? Im dealing with the same

[razvanbretoiu]

Same issue with @react-navigation/material-top-tabs @miklschmidt did you found a solution?

[miklschmidt]

Same issue with @react-navigation/material-top-tabs @miklschmidt did you found a solution?

Unfortunately not, i haven't had the time to look into it thoroughly.

[s-rayed]

@razvanbretoiu I ended up removing the top tab navigator and used a custom ui component, but you can just as easily replace with a tabs component from native base which I believe uses react native swipeable tabs. I realized its actually a bit overkill to nest another navigator just for the top bar navigation. The props on the tabs component more than suffice for most use cases, hopefully for yours as well.

[dandre-hound]

Bummer, we use @react-navigation/material-top-tabs so that we can deep link our users to different tabs. We're about to add a second news feed alongside our main feed and they will both live under a tab navigator, so our shared element transitions are going to break.