Crashing on re-navigating to second page.

Question

Crashing on re-navigating to second page.

Phunction 301

I have a crashing issue I can't figure out. From my main page I have a button that opens a second page:

await Shell.Current.GoToAsync("newPage");

That second page is setup as a tabbed layout with 2 tabs, both tabs are content pages, one contains a grid the other contains a drawable.

On the first time, it will work fine, on the second time I get the error:

Microsoft.UI.Xaml.Controls.Frame.NavigationFailed was unhandled.

Even if I leave the Draw() method on my drawable blank so it essentials does nothing.

However, if I add a simple Thread.Sleep(500) to the constructor on the drawable, it will work fine and I can open the page over and over.

I am not sure what could be happening, for some reason on the second try (without the pause) it crashes, it seems like it is trying to clear something up but not fast enough? Is there a way to force the app to release everything on navigating back from newPage? It never c rashes on the first open, or as I stated, if I add a pause.

Anonymous

2024-02-01T02:45:22.7066667+00:00

If you are adding Thread.Sleep(500) resolves the issue indicates that some asynchronous operations might not be completing before you attempt to navigate to the new page for the second time.

Firstly, please ensure that all asynchronous operations are properly awaited. If there are any asynchronous tasks that are not awaited, it could lead to unpredictable behavior.

Next, do you have event handlers or messages subscribed to in your navigated pages? Ensure that you unsubscribe from those events when the page is disposed or when navigating away.

one contains a grid the other contains a drawable.

Do you create a GraphicsView in this navigated page? Can you remove this drawable for testing? if it is working.
Phunction 301 Reputation points

2024-02-05T03:28:43.7966667+00:00

OK, even with the drawable removed it will still crash. But I did find one thing, the drawable is on the second nav page. If I go back while showing the first page it is fine, I can switch between both pages, as long as I navigate back with the first page showing, it will work. If I navigate back with the second page showing, then try to go back it will crash. Adding a thread timer does not actually make a difference. Removing the drawable so it is just a blank content page will still crash.
Anonymous

2024-02-05T09:27:24.9033333+00:00

Could you share a minimize demo to just what is needed to reproduce the problem?
Phunction 301 Reputation points

2024-02-13T18:12:18.4566667+00:00
Ok, that is interesting, it does not matter what content pages there are, even if both pages are just basic empty content pages, if I navigate back from any tab page other then the first, it will crash when I try to go back to that page. If I do this then I can go back without error:

protected override bool OnBackButtonPressed() { this.CurrentPage = this.Children[0]; return base.OnBackButtonPressed(); }

(the page flow is MainPage -> tabbed navigation page with tabs 1,2,3, etc. going back to MainPage when viewing tab 1 then openening tabbed page is fine, leaving an 2, 3, etc, going back to tabbed page crashes)
Anonymous

2024-02-19T08:43:28.9466667+00:00

Do you used AppShell and Tabbedpage at the same time? Which .NET version that you use? I tried to reproduce this issue; can you share with us reproduced steps?

Your answer

Anonymous

2024-02-01T02:45:22.7066667+00:00

If you are adding Thread.Sleep(500) resolves the issue indicates that some asynchronous operations might not be completing before you attempt to navigate to the new page for the second time.

Firstly, please ensure that all asynchronous operations are properly awaited. If there are any asynchronous tasks that are not awaited, it could lead to unpredictable behavior.

Next, do you have event handlers or messages subscribed to in your navigated pages? Ensure that you unsubscribe from those events when the page is disposed or when navigating away.

one contains a grid the other contains a drawable.

Do you create a GraphicsView in this navigated page? Can you remove this drawable for testing? if it is working.
Phunction 301 Reputation points

2024-02-05T03:28:43.7966667+00:00

OK, even with the drawable removed it will still crash. But I did find one thing, the drawable is on the second nav page. If I go back while showing the first page it is fine, I can switch between both pages, as long as I navigate back with the first page showing, it will work. If I navigate back with the second page showing, then try to go back it will crash. Adding a thread timer does not actually make a difference. Removing the drawable so it is just a blank content page will still crash.
Anonymous

2024-02-05T09:27:24.9033333+00:00

Could you share a minimize demo to just what is needed to reproduce the problem?
Phunction 301 Reputation points

2024-02-13T18:12:18.4566667+00:00

Ok, that is interesting, it does not matter what content pages there are, even if both pages are just basic empty content pages, if I navigate back from any tab page other then the first, it will crash when I try to go back to that page. If I do this then I can go back without error:

protected override bool OnBackButtonPressed() { this.CurrentPage = this.Children[0]; return base.OnBackButtonPressed(); }

(the page flow is MainPage -> tabbed navigation page with tabs 1,2,3, etc. going back to MainPage when viewing tab 1 then openening tabbed page is fine, leaving an 2, 3, etc, going back to tabbed page crashes)
Anonymous

2024-02-19T08:43:28.9466667+00:00

Do you used AppShell and Tabbedpage at the same time? Which .NET version that you use? I tried to reproduce this issue; can you share with us reproduced steps?

Share via

Crashing on re-navigating to second page.

Your answer