Giters

PrismLibrary / Prism

Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Android "hardware" back button closes the app when app contains a tabbed page with a navigation page as root page for one of the tabs, Take 2

skha83 opened this issue · comments

commented

Description

Sorry for creating another issue with more or less the same problem as was closed in #3095.
I have tried the navigation changes introduced in version 9.0.436-pre which should resolve issue #3095. I'm still having problems getting the navigation to work the way I expect it to work. And in one of the scenarios it work worse than before the change (scenario 1 below).
I have created a fork on the current Prism main and simplified my example so it only contain one tabbed page with a navigation page and two segments here https://github.com/skha83/Prism

The example code is modified like the following:

.CreateWindow(nav => nav.CreateBuilder()
    .AddTabbedSegment(page =>
            page.CreateTab(t =>
                t.AddNavigationPage()
                 .AddSegment("ViewA")
                 .AddSegment("ViewB")))
    .NavigateAsync())

Steps to Reproduce

I have two scenarios and both of them fail.

Scenario 1.

  1. Deploy and launch the PrismMauiDemo app from my repository on an Android phone ( tested on Samsung Galaxy S24 Ultra).
  2. The app is launched with ViewB page on top and ViewA and NavigationPage below.
  3. Press the hardware back button.

Expected result:
The app will navigate from ViewB -> ViewA but stay in foreground so ViewA is visible.

Actual result:
The app navigates to ViewA but immediately backgrounds the app. When the app is opened again ViewA is the current window. But the app is not terminated.

Scenario 2.

  1. Deploy and launch the PrismMauiDemo app from my repository on an Android phone (tested on Samsung Galaxy S24 Ultra).
  2. The app is launched with ViewB page on top and ViewA and NavigationPage below.
  3. Press the software navigate back button on the top left of the app, so it navigates back to ViewA.
  4. When ViewA is visible press the hardware back button.

Expected result:
The app will be backgrounded but not completely terminated.

Actual result:
The app gets completely terminated and needs to be relaunched and is started from scratch.

The behavior in scenario 1 is different from before the new changes introduced to fix issue #3095. Previously it would correctly navigate from ViewB -> ViewA and not background the app if the hardware back button is only pressed once.

Scenario 2 is working in the same way as before the recent changes.

Platform with bug

.NET MAUI

Affected platforms

iOS, Android

Did you find any workaround?

It seems like maonaoda have made some workaround #2990 (comment), but that requires introducing a custom NavigationPage class and then it is no longer possible to use the extension methods on the NavigationBuilder like AddNavigationPage. I would prefer this basic scenario worked "out of the box" so people wouldn't have to look around for a hack. I have not verified if his fix would work in my scenario.

Relevant log output

No response

commented

Same problem !