Rebuild Component and Rebuild Page actions fail to update component UI from parameters

[proptechbex]

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

The "Rebuild Current Component" and "Rebuild Containing Page" actions are not functioning as expected. They fail to force a component's UI to update when its input parameters change. This core issue prevents the creation of reactive components and can be demonstrated using a TextField that should update its value from a component parameter.

Expected Behavior

When a component parameter is updated, any widget inside that component that uses the parameter (like a TextField's initial value) should reflect that new value after a rebuild action is triggered.

Steps to Reproduce

Public Project Link
You can clone the project and reproduce the bug using the following link:
https://app.flutterflow.io/project/rebuildreportbug-s9art4

Steps To Reproduce:

1. Create a Page: Start with a new blank page.

2. Create a Page State Variable: Create a local page state variable, for example, selectedValue (String).

3. Add a Dropdown: Add a DropDown widget to the page. Configure its onSelect action to update the selectedValue page state variable with the value from the dropdown.

4. Create a Custom Component:

• Create a new component.
• Add a component parameter, for example, inputText (String).
• Inside the component, add a TextField widget.
• Add two buttons with the labels "Rebuild component" and "Rebuild page". The first button triggers the "Rebuild Current Component" action, and the second triggers the "Rebuild Containing Page" action.

5. Configure the TextField (Two Attempts):

• Attempt A: Set the Initial Value of the TextField directly from the inputText component parameter.
• Attempt B: Add an onInit action to the component that uses "Set Form Field" to set the TextField's value from the inputText component parameter.
• (Note: Neither of these methods works; the bug is present in both cases.)

6. Assemble on the Page:

• Add the custom component to the main page.
• Pass the selectedValue page state variable as the parameter for inputText.

7. Run and Test:

• Run the app in Test Mode.
• Select a value from the DropDown. The page state variable updates correctly.
• Observe that the TextField inside the component does not update to show the new value.
• Click the "Rebuild component" and "Rebuild page" buttons. Observe that even with these explicit rebuild triggers, the TextField value remains unchanged.

Reproducible from Blank

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

Bug Report Code (Required)

IT4ChvHlw85NofVb15DubsExhmAsH1whRY0w19Zxa0g3DZPND+x/esnRQFJuZ9OrdghhMWKWpHsKpqCMm9z1U/ddYDqYfJRR+s9+ZQmVWkSXVc21PpCefkFUGshbJmqE1qejgBBDIrB1c3AD3U2mDN6REyvUO4TIDUQZGfyKBNvXrgfuQ0SLb3kNh1JWeC/v

Visual documentation

The following images illustrate the issue. The page state updates correctly, but the component's UI fails to reflect this new state, even after explicitly triggering rebuild actions. You can also drag and drop these files directly into the GitHub issue form.

• Initial State: The DropDown shows "Option 1". The expected value text updates correctly, but the TextField inside the component does not.

• State Change with No Effect: After selecting "Option 2", the TextField remains unchanged. Critically, clicking the "Rebuild component" and "Rebuild page" buttons has no effect.

• Consistent Failure: The bug persists with "Option 3", confirming the failure of the rebuild actions to update the component's UI from its parameters.

Environment

- FlutterFlow version: Flutterflow v6.3.12+ realeased September 17, 2025
- Platform: Web
- Browser name and version: Chrome Versión 140.0.7339.128 (Build oficial) (64 bits)
- Operating system and version affected: Windows 11 Pro 24H2

Additional Information

This issue has a critical impact as it fundamentally breaks the ability to create reactive, reusable components. Without the ability to reliably update a component's UI from its parameters, developers are forced to use complex workarounds (like custom actions that navigate back to the same page to force a full reload) or avoid using components altogether for dynamic content. This severely limits the modularity and scalability of applications built in FlutterFlow.

[Juansarmi]

Hi there!

I'm sorry to hear you're experiencing this issue. I tried to reproduce it on my end but couldn't replicate the problem.

It seems that the issue with the text field might be related to how the initialValue behaves differently compared to, for example, the hintText or a regular Text widget.

To update the value of the text field inside your component, you can set an action on the page that contains the component — in your case, specifically on the dropdown. There, you can add a setFormField action, select the appropriate text field, and assign it the value you want — without depending on the parameters passed to the component.

I've also attached a video to help illustrate the steps.

Hope this helps!
Best regards.

setFormField.mp4

setFormFieldTEST.mp4

[proptechbex]

Hello @Juansarmi,

Thank you for the quick response and for looking into this.

I appreciate you providing a video with a workaround. While using a setFormField action directly from the page does indeed update the text field, I believe there is a misunderstanding of the core issue I am reporting.

The solution you proposed is a workaround that bypasses the component's parameter system entirely. The fundamental purpose of a component is to be a reusable, encapsulated widget that reacts to changes in its input parameters. A page should not need to know about the internal implementation details of a component (like the specific name of a TextField inside it).

The central bug is not with the TextField itself. The TextField and the sample project were created as a minimal, isolated example to clearly demonstrate that the Rebuild Component and Rebuild Containing Page actions are failing.

The core issue remains:

A component's UI does not update when its input parameters change, even when Rebuild Component or Rebuild Page actions are explicitly triggered.

To put this into the context of my real-world application: the workaround is not a viable option. I am building a complex web app that relies on over 70 individual components. Each of these components has its own internal logic and performs calculations when its parameters change. The entire architecture is based on these components being reactive and self-contained. It is simply not feasible to have the page manually use setFormField to update every single value inside every component; it would defeat the entire purpose of building a modular application and make the project unmanageable.

This is a critical issue because it breaks the reactive nature of components, which is essential for building any scalable or complex application.

Could you please re-examine the issue from the perspective that the rebuild actions are failing to propagate parameter changes to the component's UI? The public project I provided clearly demonstrates this failure in functionality.

Thank you again for your help.