navigation action with replace route property leads to a side effect. page A is displaid few milliseconds before navigate to page C

[alcaribou]

Can we access your project?

• 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

Hello,

There is a bug (side effect) when using replace route property in navigation action.
Page A -> Page B -> Page C (replace route) when navigate to the page B the page A is displaid during few milliseconds before page C (bad side effect)... :(

Expected Behavior

Page must not be displaid until we go back.

Steps to Reproduce

1. Create a page A with a button to navigate to page B
2. Create a page B with onLoad action and add 1 action of delay of time and one action navigate to page C with replace route property set.
3. Create a page C

execute.
click on button page A to go to page B, few seconds after the onload execute the navigation to page C but just before displaying page C the page A is displaid and replace by C. bad effect...

Reproducible from Blank

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

Bug Report Code (Required)

IT8wlsn1z4pNj7xF7aXiacdFimAUJjM6RY03juxuWRAgfY/qPbN/PsnRU1ZpZ+6oSmw7Ikamjl8Jpt7ShtmeEfkpaUiVUb581ZAMWAH1e167Sr6lEc2KeHRABedmGWHE5sGRnSNTPsZuck0lxk61fd7KTj/qH77HO1cBOfqiFLrDpF65KxD3JhREshQOMEfVBvQbIVDq+f6QspZl1eTjzw==

Visual documentation

see attached video. the "Go To Page B" is displaid few milliseconds until page C is displaid.
https://github.com/user-attachments/assets/4190446c-7b6f-46b6-b554-b9b6dfe07c34

Environment

- FlutterFlow version: 6.4.71  / flutter 3.32.4
- Platform: web or apk
- Browser name and version: chrome or apk android
- Operating system and version affected:  windows or android

Additional Information

No response

[Alezanello]

Hello!!

Thanks a lot for this insight. While investigating why this happens, it appears to be a common behavior when using GoRouter (our navigation package). We found similar reports, such as this one:
https://stackoverflow.com/questions/78558311/flutter-go-router-re-render-previous-page-when-navigate-with-pushnamed, along with others across the web.

I’m going to pass this issue along to the engineering team so we can discuss how to prevent this behavior while still using the package. As a possible workaround, you might also try changing the transition type—using Instant instead of Fade or similar transitions may help reduce the brief reappearance of Page A.