Xamarin.Forms navigating from tab to another tab

[Arbalets]

Description

I have converted my project from Prism 6.3. Everything is working fine except navigating from TabbedPage tab to another tab in the same page.
I have a MasterDetail page from where I can navigate to all the TabbedPage tabs.

In 6.3 I had there following:

NavigationPage/MyTabbedPage/TabPageA
NavigationPage/MyTabbedPage/TabPageB
NavigationPage/MyTabbedPage/TabPageC

I replaced them with:

NavigationPage/MyTabbedPage?selectedTab=TabPageA
NavigationPage/MyTabbedPage?selectedTab=TabPageB
NavigationPage/MyTabbedPage?selectedTab=TabPageC

Steps to Reproduce

When navigation from another page everything works fine, but when already in some of the tabs and trying to navigate to another tab (from MasterDetail) nothing happens.

Expected Behavior

Go to the selected tab.

Actual Behavior

Nothing happens.

Basic Information

• Version with issue: 7.0.0.362
• Last known good version: 6.3
• Xamarin.Forms version: 2.5.0.122203

[brianlagunas]

Oh wait... I had to re-read that. I see that you are navigating from a MasterDetailPage, not from within the actual TabbedPage. This is actually a very interesting scenario. Can you please provide a sample app that sets up the scenario that I can use to test the behavior out?

[Arbalets]

Sure, here you go: https://github.com/Arbalets/TabNavigation
I've included 6.3 sample as well, just for comparison.

[brianlagunas]

Done. You can test it out in the latest CI builds on MyGet, or wait for the SR release.

[Arbalets]

Thanks

[dazinator]

I just updated from 7.0.0.362 to 7.0.0.396 and wanted to confirm that it solved my problem, which was: When navigating to a tabbed page, the default content page (tab) would be displayed. however it's viewmodel was not activated by prism and so it's UI was not data bound. After the NuGet package update to latest version it worked. Thank you.

[dazinator]

Turns out I spoke to soon, the issue was not completely resolved after upgrading. I think perhaps the fix wasn't in 7.0.0.396. I'll await the next release!

[brianlagunas]

The fix is not on Nuget, it's in our CI feed.

[dazinator]

Ok great, I have grabbed the CI package, working as expected now, thanks

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.