Skip to content

[NET 10] Shell Navigation Bar Remains Visible After Navigating Back to ContentPage with NavBar Hidden (iOS Only) #32583

@amitfinova-ai

Description

@amitfinova-ai

Description

On iOS, when navigating from a ContentPage with the Shell navigation bar hidden (Shell.SetNavBarIsVisible(this, false)) and Shell Flyout disabled (contains a content view that has the navigation button), to another ContentPage with the navigation bar visible (Shell.SetNavBarIsVisible(this, true)), navigating back causes the navigation bar to remain visible on the original page, even though it should be hidden.

Image Image Image
Screen.Recording.2025-11-13.at.3.37.08.PM.mov

Steps to Reproduce

Repos: ShellSpacingIssue.zip

  1. Create a .NET MAUI Shell app.
  2. Set up a ContentPage Page A (Main Page) that contains a content view and Shell Navbar visibility set as false and Shell Flyout behaviour set as disabled.
  3. Content view contains the button to navigate to a Page B (content page) let's message page.
  4. Page B ( message page) has the Shell navigation bar visible.
  5. Run the app on iOS.
  6. Navigate from Page A (Main Page) to Page B (Message Page) using the button.
  7. Navigate back to Page A (Main Page)

Expected Behavior:
When returning to Page A, the Shell navigation bar should remain hidden.

Actual Behavior:
On iOS, the Shell navigation bar is visible on Page A after navigating back.

Link to public reproduction project repository

No response

Version with bug

10.0.10

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

No response

Affected platforms

iOS

Affected platform versions

iOS

Did you find any workaround?

No response

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-controls-shellShell Navigation, Routes, Tabs, Flyouti/regressionThis issue described a confirmed regression on a currently supported versionpartner/syncfusionIssues / PR's with Syncfusion collaborationregressed-in-10-preview1s/triagedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't working

    Type

    No type

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions