MAUI App navigation and messaging not working since update to .NET 8

Leonardo D’Incau 0

I am having this error 'No destination with ID 10 is on the NavController's back stack. The current destination is Destination(0x5) class=crc6452ffdc5b34af3a0f.NavigationViewFragment' since I updated my app from .net7 to .net 8 due to the urge of Google Play store to set Android Framework target to 14. In particular, it happens every time i try to perform a pop in my app, even if the NavigationStack is not empty. In fact, the page is correctly popped (at least visually) but this exception in thrown and it prevents the app from functioning properly (I use wekreferencemessenger to send a message from the page that is popped to the previous one and after updating to .net8 and getting this error the message is no longer received). All of this works perfectly in .NET7 and even if doing a manual downgrade again from the broken .NET8 one to .NET 7
Please give a solution because this error is preventing us from updating the app on the store before the limit imposed by Google.

Leon Lu (Shanghai Wicresoft Co,.Ltd.) 74,801 Reputation points Microsoft Vendor

2024-09-25T05:57:17.1+00:00

No destination with ID 10 is on the NavController's back stack. The current destination is Destination(0x5) class=crc6452ffdc5b34af3a0f.NavigationViewFragment'

Does this error happen in the release mode or debug mode?

it happens every time i try to perform a pop in my app, even if the NavigationStack is not empty.

Can you share this part of code?

I use wekreferencemessenger to send a message from the page that is popped to the previous one

Why you need to use weakreferencemessenger to transfer data back to the previous page? If you use popup from cummunity toolkit, you can return value directly by CloseAsync method.
Leonardo D’Incau 0 Reputation points

2024-09-25T06:47:02.0833333+00:00
The error happens both in release and in debug mode.
I use the weakreferencemessenger because it was used in the previous version of the project and we had no time to change the code, also it worked well before updating to .NET 8 so we weren't interested in changing it. Also, we don't want to have a Popup, we prefer to push to a new page since the user has to make multiple operation before popping to the previous page.

Since you asked, i will attach a sample of the weakreferencemessenger used (i would like to point out that its logic works because the message is sent and received, but i think that the above error about navcontroller prevents the correct behavior of it)

On the page that will be popped:

Message message = new Message() { Item = selectedItem }; WeakReferenceMessenger.Default.Send(message); //pops page inside the detail of my flouytpage await ((NavigationPage)((FlyoutPage)App.Current.MainPage).Detail).PopAsync(true);

On the page that is reached after the pop:

public void Receive(Message message) { //assign the message content to the actual page variable (binded to the xaml) this.ReceivedItem = message.Item; //...other operations of my app using the messsage data //... }

Share via

MAUI App navigation and messaging not working since update to .NET 8

Your answer