FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
127 stars 26 forks source link

Can't change action variable if it's value has an error #3851

Open zachary-ferioli opened 1 month ago

zachary-ferioli commented 1 month ago

Can we access your project?

Current Behavior

When a variable in one action is reliant on the output of a previous action, and that previous action changes/is removed, when a user goes to change/fix this bad variable value, there is a big grey box in place of the value dropdown (null value likely)

Expected Behavior

If a variable in an action has an error, the user should be able to go in and change it without this grey box being in the way.

Steps to Reproduce

  1. Create an action block that has some sort of action output
  2. Create another action block after that with a variable
  3. This variables value should then be set to an action output value from the previous action
  4. Either change or delete the first action which supplies the action output
  5. Attempt to change the variable error in the second action to see the grey box

Reproducible from Blank

Bug Report Code (Required)

IT4Kl/KAx4lIobgA7aryacFFoGAQIjsnap08lsBtTQ8gIoCsG7YAW/SkQE9WZ7yhdH03J06JrzoKwMqPvfbIN8IFCAeZboQ5zrh+VT3wXTmXMJjXDpDteEQkMNpKBUC656enrCJRKbd1V1Ib7Ga2BvC+fCjrNJzqPDMnG86ZIZ3JnXfuQ0SLb3kNh1JWeC/v

Visual documentation

image image

Environment

- FlutterFlow version: v5.0
- Platform: Windows 11
- Browser name and version: Google Chrome 131.0.6724.0
- Operating system and version affected: Windows 11 (up to date version)

Additional Information

I need to change an API call to a Supabase query to fix a bug in my authentication flow. I'm blocked by this error in FF.

paulperez-dev commented 1 month ago

Hi @zachary-ferioli,

I wasn’t able to reproduce the issue on my project (recording an audio), but it is replicable on yours. I’ll forward this to the engineering team so they can look into it.

Thank you for your patience!

github-actions[bot] commented 1 month ago

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.