Consistent Issues With Component Callback Parameters

MartinLockheart commented 3 weeks ago

Can we access your project?

[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

Trying to pass documents/document references/custom data through callback parameters from within components often (if not always) results in build failures.

Issue reproduced in blank project: https://app.flutterflow.io/project/list-data-bug-component-eyxpqh?tab=widgetTree&component=myCustomComponent

Expected Behavior

I should be able to use documents/references/custom data types in my callback actions.

Steps to Reproduce

Create a new project
Create a custom datatype and add any data fields
Create a two components, one for the list item and one to be a subcomponent of the list item.
Add callback actions to both components, which use the custom datatype in the callback action
Run build

Reproducible from Blank

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

Bug Report Code (Required)

IT5TjMrqx89god9Y0Lr9bfpsmj45JkQ5a40/lO1Edw0dDOvyO4YueM7BYXFJYcukTFVcIWKZ/Wcz+KHIueP9VuwrBxSWU4NeyapUewrKQXGQbq6qDaWWY0YmI51XI0CP56WGmA9QHMZsdE4ZwGCuH96tExfqQePpOTM0AMilIpv7+myULhDBUyZrxmNecCfn

Visual documentation

Screenshot of issue from blank project: 3-failed-build

Screenshot of most recent issue from one of my other projects:

Environment

- FlutterFlow version: 4.1.59
- Platform: Web
- Browser name and version: Chrome, 126.0.6478.56
- Operating system and version affected: Windows 11

Additional Information

I've been dealing with this issue for almost a month now. I've talked with support about it twice, with no updates. I have multiple projects that have been delayed for weeks because of this, and I don't know what else to do at this point besides post the issue here.

I've managed to create workarounds for some of the issues this has caused, but not even being able to pass a document through a callback parameter is very frustrating - especially considering that recursive components were just released, while this issue has been active for nearly a month.

paulperez-dev commented 3 weeks ago

Hi @MartinLockheart! We recently upgraded the dependencies, can you please verify if this guide helps you?

MartinLockheart commented 3 weeks ago

Sorry for any confusion, but I recreated this issue in a blank project and linked it above. I don't have any custom code in that blank project that could be causing dependency issues. Is there something I'm missing about how dependency upgrades work with native Flutterflow functionality?

MartinLockheart commented 3 weeks ago

Here's some new information after continuing to test in the blank project linked above:

1) In the component "myListItem", in the action parameter "updateParentData", the build error goes away when the parameter "updatedData" is set to "nullable". If it is not set to nullable, the build fails.

2) In this same project, there's an additional bug where attempting to pass list data into a sub-component parameter results in a "data (unknown)" bug. This can be seen in the projeect by doing the following:

A) Select "myListItem" in "myCustomComponent" B) Select the variable for the "myListItem" parameter "itemExistsInOtherLists" and attempt to pass "otherListOfCustomData" (either from the app state variable or the "myCustomComponent" parameter). Select "listContainsItem", and you will be unable to select the custom datatype in that the list is composed of. Instead, it says "Data (Unknown)".

Here's an additional screenshot for that bug: