-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Push FlyoutPage resetStack: true does not set the root page as flyout on Android. #808
Comments
Also a link to the Slack question I left a while ago :( https://reactivex.slack.com/archives/C02AJB872/p1725410970584099 |
UPDATE: I've been poking around with the Main page and NavigationView. It seems that when I Navigate to the Root Flyout page, Sextant is converting it to its own NavigationView. I did this:
The app does navigate to the FlyoutPage on Android. HOWEVER, this is messing something up on the stack, because I start getting all sorts of random exceptions(When I switch back to the MainViewModel as the root). :( |
UPDATE 2 After doing the above to navigate the to Root Flyout I try to "Logout", by Navigating to the MainViewModel again:
But then I get this exception. Not sure what to do next here :(
|
I went to check if a Plain Maui sample would work. It does not have dependencies on sextant or reactiveUI. This is where navigation happens: Also the MainPage is a straight up FlyoutPage, no ReactivePage. And the Loged in Page is just a ContentPage With plain Maui components, the navigation works as expected on iOS and Android =/
|
I think Chris put up his hand to help with this one. The indepth analysis definitely helps |
Hi I have taken a look and can see your issues, I will have to carry on looking at this over the next few days, I will try to find a resolution to the issues. |
Thank you everyone. I will also keep poking around to see if I can bring more info here. |
Hi @ChrisPulman, were you able to have a look at the issue? Let me know if there is anything I can do to help. |
Hello folk. I'm back to check if there are any news on this bug. Please let me know if there is anything I can to to help. |
Hey Y'all. Just coming back to tell you that I opened a ticket with don't MAUI. I dove deeper in the Sextant code just to find out that the problem seems to be here: Sextant/src/Sextant.Maui/NavigationView.cs Line 184 in e221e44
I also found the same exact issue from a different person, and the ticket has been open for over a year. I don't think the MAUI folk will go anywhere with it. So either we'll need to figure out a way to change the root of the app and trash/recycle the NavigationPage somehow. |
Describe the bug 🐞
I'm using sextant to create a simple Login Page -> Logedin Page app.
FIrst a simple root Navigation page where the app first navigates to.
After, the user clicks on Login Button and the app navigates to a classic FlyoutPage.
The issue I see is specific on Android. When I navigate to the Flyout page, it just acts as if its a Navigation Page.
Step to reproduce
https://github.com/DanielCauser/SextantNavigation/blob/main/SextantNavigation/App.xaml.cs#L21
https://github.com/DanielCauser/SextantNavigation/blob/main/SextantNavigation/MainViewModel.cs#L17
Reproduction repository
https://github.com/DanielCauser/SextantNavigation
Expected behavior
When you clean the stack, and navigate to Flyout Page, the flyout popover behaviour should work.
Screenshots 🖼️
User lands on pretty Login page.
Once user Logs in, they navigate to the flyoutpage (For the life of me I can't make the hamburger button show, but the flyout page behaviour is there):
However on Android, the apps just navigates to the Flyout -> Detail page and gets stuck there. No Flyout popoover behaviour happens.
IDE
Visual Studio 2022
Operating system
Mac
Version
3.0.1
Device
Any Android Device
ReactiveUI Version
ReactiveUI.Maui" Version="20.1.1"
Additional information ℹ️
No response
The text was updated successfully, but these errors were encountered: