PushNewNavigationServiceModal not showing the back button

[dpedrinha]

Hi.

Here's the scenario.

I have a FreshTabbedFONavigationContainer with 3 tabs.

If I PushNewNavigationServiceModal from one of the 3 tabs, the new navigation page doesn't show the back button.

If I navigate deeper from one of the 3 first tabs with PushPageModel, then call PushNewNavigationServiceModal from the new page, it adds the back button and works as expected.

Any idea why and how to fix it?

Thanks

[rid00z]

@dpedrinha If possible you should download the FreshMvvm source code and review the sample app, this will give you a better understanding of how to do Navigation in Xamarin.Forms and FreshMvvm. Otherwise you can provide a sample application and I can take a look.

[dpedrinha]

@rid00z I can't test your samples because they are using .Net versions that I don't have installed and I can't install due to lack of space in my SSD. But I checked it and did my best to mimic what you did there. So I made a sample app for you to see the problem, here's the link: https://www.dropbox.com/s/1evujo6owbrv63r/navigationbackbuttontest.zip?dl=0

I haven't tested the iOS version because I don't have my Mac right now.

But i did test it on Android and Windows 10. On Android the problem I'm facing isn't a problem because it has a hardware back button. So the problem is on Windows and iOS versions.

You will notice that I made a custom NavigationContainer. And this is where the problem happens. If I open this NavigationContainer from the first page on my app, it doesn't add the back button to it, but if I open it from a deeper page, it does appear.

On the first app page you have two buttons, one to open the custom NavContainer and another one to navigate deeper (MiddlePage).

If you navigate to the MiddlePage, there you can open the NavContainer too. If you do, the back button appears. If you do it from the first page, it doesn't.

And I know, you have a built-in tabbed navigation container but I need a custom one. I'm pretty sure the problem isn't there.

[dpedrinha]

@rid00z Did you test the example?

[dpedrinha]

I did as requested and created you a sample. Two months later and I didn't get any response. Not cool.

[rid00z]

@dpedrinha I've reviewed the sample and it functions without issues. There will never be a NavigationBar when you push the CarouselFreshMVVMNavPage because it's not inside a Navigation page.

[dpedrinha]

@rid00z so you are telling me that FreshTabbedFONavigationContainer is not a Navigation page?

If you look carefully, your statement that "there will never be a NavigationBar" is not true because the sample itself shows how the NavigationBar does appear if CarouselFreshMVVMNavPage is called from any page besides the first one. No new Navigation page created in between.

[nichojo89]

Is this getting fixed? I feel like i'm now being pushed to switch to a different framework in 2020.

[rid00z]

Can you describe the issue your having? What is the structure of the pages and navigation? Do you have a sample to test?

On Mon, 27 Jan 2020 at 12:18 pm, Jon Nichols [email protected] wrote:

Is this getting fixed? I feel like i'm now being pushed to switch to a different framework in 2020.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rid00z/FreshMvvm/issues/168?email_source=notifications&email_token=AALZPPMUF5MTXMVLTKAC2HLQ7YY6JA5CNFSM4DRPHT3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6DBYQ#issuecomment-578564322, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALZPPLE37PADJLWP6LHFGTQ7YY6JANCNFSM4DRPHT3A .

-- Michael Ridland co-CEO XAM Consulting xam-consulting.com