NavBar disappears when navigating to a page with parameters

[localbasejp]

Has your issue been reported?

• [X] I have searched the existing issues and confirm it has not been reported.
• [X] I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When I navigate to a page with a NavBar using a button action everything seems fine. The problem starts when I try to pass some parameters to that page. Then, it navigates to that page, parameters seem to be present in there, but the navbar is absent. Tried to debug it with a console, but it shows nothing wrong. Also tried with different NavBar and the issue stays the same. The moment I stop passing parameters to that page while navigating, it works as it should, showing navBar. Do You have any ideas what I'm doing wrong?

Expected Behavior

NavBar is displayed even after specifying parameters and transitioning to Page B

Steps to Reproduce

1. There is a Page B that has a TabBar widget, and Page B receives a parameter of tabIndex(Integer). Page B displays the Nav Bar.The initial Tab Index of Page B's TabBar specifies the tabIndex parameter.
2. Specify the TabBar Index with the tabIndex parameter to transition from Page A to Page B.
3. Page B Nav Bar disappears when parameters are specified
4. If no parameter is specified, Page B's Nav Bar will be displayed.

Reproducible from Blank

• [X] The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITFfl/Lf8ZNgrttY1a6JbsEwhiI4Nm0cTeQvitZCaxAaI+PuO7QfduCkUxZVcuqHYAhDfWGJ/T0y+Nr7v+zXLuw7Aymafr5fypZTUxDhVlK6b5iKCZG8SkdBL8NPJna11ruNnB1DBPpecl4f1Ga6CuuAb3qCf9qOYwx5e6fDbOY=

Context

Service operability will be significantly impaired.

Visual documentation

https://github.com/FlutterFlow/flutterflow-issues/assets/93519126/878d0904-4c9b-4c43-82e0-a2c0e0952aaf

Additional Info

No response

Environment

- FlutterFlow version: v4.1.53+
- Platform:Mac
- Browser name and version:Chrome 124.0.6367.208（Official Build） （arm64）
- Operating system and version affected: Apple M1 Pro 14.4.1（23E224）

General

• [ ] I was collaborating with other users in the same project prior to data loss
• [ ] I navigated between different project views leading up to data loss
• [ ] The UI was running very slowly prior to data loss
• [ ] A crash or other bug occurred prior to data loss
• [ ] Data was not saved in a snapshot
• [ ] I was using flutterflow from multiple devices
• [ ] I was using flutterflow from multiple platforms (e.g. both web and MacOS Desktop app)

Relative to the time the changes were made, data was lost within

• [ ] 1 minute
• [ ] 1 hour
• [ ] 1 day
• [ ] 1 week

When following my steps to reproduce, data loss happens

• [ ] ~100% of the time
• [ ] ~50% of the time
• [ ] ~10% of the time
• [ ] ~1% of the time
• [ ] Very rarely or only encountered once

[ignalauret]

Hey @localbasejp thanks for your report. I can confirm that the behaviour of the Navigation to a page that is part of the NavBar is not the expected. I will send this to our technical team so they can take a look. They will keep you updated on this thread. Have a great day!

[Robert-kWhBot]

@ignalauret this is still an issue but it appears no one is assigned to this issue.

[LeCause]

@ignalauret Are there already any updates on solving the issue? Thanks in advance!

[cdolan92]

+1 for visibility, this is a very frustrating bug that makes parameters unusable in many situations :(

[wenkaifan0720]

Hi. I confirmed with the team and this is the expected behavior. Pages with nav bars should be considered as the same page (similar to a tab bar view) with the current design. We should give a user a better warning if they are trying to pass parameters to a page with parameters. We are doing this because we don't want to avoid page rebuild and page transition effects when you switch pages using the nav bar.

[Robert-kWhBot]

That doesn't make sense at all. Navigation is between pages, not a tab control. Just rebuild the page if the parameter changes, EZ.

[cdolan92]

A friend of mine said "I can't believe you are even able to pass a parameter like this - FF params have not typically been allowed on pages with a navbar"

I had to figure out a different workaround (OnPageLoad I just reload the view every time...)

Wish this worked. I agree it makes no sense to me that this couldn't be possible

I think the intended use case for this needs to be better documented.