callback parameters not showing on components with widget builder param when using conditional values

[jobsalecperry-dev]

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

I am currently using a component with a widget builder parameter. When I bind that parameter to a series of components using conditional values, I am encountering an issue with components that have callback actions. When I go into the action editor to bind the callback parameter to, in this case, a local state variable on the current page, the callback parameters do not appear as an option.

On this same component with the widget builder param, I tested this same functionality without using conditional values, only selecting a single component, and it allowed me to access my callback parameter. It just isn't working on the conditional values.

Expected Behavior

Have the callback parameter appear as a selectable option for the above case.

Steps to Reproduce

1. Create a component with an callback action param (CompCP)
2. Create another component with a widget builder param (CompWBP)
3. Create a page and add the CompWBP component to the page
4. Click the add from variable option of the CompWBP component widget builder param and select Conditional value
5. Add any "if" condition. For the "then" condition, select the CompCP component from variable.
6. Pass the callback parameter through and select "open action editor"
7. Create an action to update state (app or local). Change update type to "set value" and set value to Callback parameter value (***This is the issue here)

Reproducible from Blank

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

Bug Report Code (Required)

ITFTlPHl8YhNseFA+KrAcu5F+WYWCUMcWOdEl+tuZwgbIoznBu0ufs/eSExtZNClaVNcEVCGkT8B+OiMheHpMME5BxSrQIc51s5iZwz0e2i7R8mmEpOOVWhARMZWC3XE35mzuxYlKrZqLmQs7WaUCuu/cALDBOu/Zwh9f6PHaOI=

Visual documentation

Environment

- FlutterFlow version: v6.3.11
- Platform: FF MacApp
- Browser name and version: Chrome Version 140.0.7339.210
- Operating system and version affected: MacOS Sequoia 15.5 (24F74)

Additional Information

I cannot finish my app unless this issue is resolved!!

[Juansarmi]

Hi! Hi! Sorry to hear you're experiencing this issue.

If you’re able to recreate the issue in a brand new blank project, that would really help speed things up on our side.

Please also send me the bug report code from that new project so I can take a closer look.

Thanks in advance!

[jobsalecperry-dev]

Hey, yes I just recreated it on a blank project. Here is the bug report code for the widget on the new property:

ITESz/Hqx89gouFd7ZDudfpqhQMkQzM6bZI7ku1EdwEhNbKuEJoLOs7BdklLYteDY25qB02GkjkD7tLQivLPNvkoFyuCQJRg+a5XQRfiIU+5bKq7EqrpYXFRJJlYJ3ak1MOn3RYkHPpYckIR2E6UCvCNG3qCf9qOYwx5e6fDbOY=

[Juansarmi]

Hi again!
From what I understand, you're trying to update the pageState of the page where your component is located, using a callback inside the component — and that part is totally fine.

The issue here is that within your callback action, you can’t directly set the pageState using the callback’s return value — it simply doesn’t work that way. Instead, you should assign the pageState value based on another variable, whether it's a different parameter, state, or something else.

Please let me know if this is indeed the issue, or if there's something I might have misunderstood.
If that's the case, a short video would be very helpful.

Best regards!

Grabación de pantalla 2025-10-01 181456.mp4

[jobsalecperry-dev]

Hey,

To respond to you above, I set it up a little differently to show the example better. Let me explain what I did:

in CompCB, I gave the callback aaction parameter a parameter of type list of strings. I then set a local component state variable with type list of strings. Then I set up an on initialization component action in which I executed a callback action and bound the parameter to the local component state variable.

Now, in the main page on CompWB when I bind the Widget builder parameter... when I just bind the component without using conditional values, it lets me select the callback parameter as "list of strings" which represents the passed through component state variable. However, when I set up a conditional value where I set up some arbitrary "if" statement and then try to set the component as a value, then bind the page state variable, it does not let me access the callback parameter.

If it works by using just one component in the widget builder param, I don't see why it shouldn't work in the conditional values where I am trying to have different widgets appear under different conditions.

Does that make sense?

[Juansarmi]

Hi again!
Thanks for the additional information — I was able to identify the issue you're facing. I’ll go ahead and share this case with the engineering team so they can look into it more deeply. I’ll keep you posted as soon as I hear back.

Best regards.

[jobsalecperry-dev]

Awesome. Thanks very much!