Can we access your project?
Current Behavior
When I add a new Component Parameter to an existing component (String type, tried both Required and non-Required) via the pencil icon → "Add Parameter" → Confirm, a toast appears within a few seconds: "That would cause a breaking crash! The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you." The new parameter is then silently removed — the component reverts back to its original parameter list.
This happened identically 6+ times in a row, including:
- With the parameter set to Required: false (not just required fields)
- After a full page reload
- Even on a freshly duplicated copy of the component with zero usages/instances anywhere in the project (the duplicate itself was reverted/removed too)
This suggests the "breaking crash" detector is reverting recent project changes generally, not specifically the parameter edit — no actual layout option was changed by me when adding the parameter, so the toast message doesn't match the action taken.
Project: https://app.flutterflow.io/project/trip-mate-vbcc0n
Component affected: RequestCard (and its duplicate, RequestCardCopy)
Expected Behavior
Adding a Component Parameter should be saved normally and not trigger an unrelated "breaking crash" revert.
Steps to Reproduce
- Open a project that has an existing custom component with several Component Parameters already defined (in my case, 6).
- Select the component, click the pencil/edit icon next to "Component Parameters".
- Click "Add Parameter", enter a name and type (tested with type: String, tried both Required: true and Required: false).
- Click "Confirm".
- Within a few seconds, a toast notification appears: "That would cause a breaking crash! The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you."
- Reopen the Component Parameters panel — the newly added parameter is gone; the component is back to its original parameter count.
- Repeat steps 2-6 on a freshly duplicated copy of the same component (with zero instances/usages anywhere in the project) — same result, and the duplicate component itself also disappears from the project.
Project: https://app.flutterflow.io/project/trip-mate-vbcc0n
Component affected: RequestCard (and duplicate RequestCardCopy)
Reproducible from Blank
Bug Report Code (Required)
IT4kz8jf5YhgobxY0LrtbcdvhjosC0g6TL0Zpu0bFEggGLbrBIYMaffOblVVXbC5dGxfeFu0nTgfxvfqj/PLNvA5HAeBQYhIyM8JTQ7JTkChbLaUBaiVfW1TJJpRCXK506SnvyJdKtRacXw13WDzOvOicAzAJpDEIFQjHuabLdeK2SrDX1iXc2URm05KZDPz
Visual documentation
When clicking Confirm after adding a new Component Parameter (e.g. name: requestId, type: String) on the RequestCard component, a toast appears at the bottom of the FlutterFlow editor within a few seconds reading: "That would cause a breaking crash! The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you." Reopening the Component Parameters panel afterwards shows the new parameter is gone.
Environment
- FlutterFlow version: current (web editor, project trip-mate-vbcc0n)
- Platform: Web
- Browser name and version: Google Chrome (latest)
- Operating system and version affected: macOS
Additional Information
This bug blocks development of the join-request approval feature — I can't add the parameters needed to wire up Approve/Decline actions on the RequestCard component.
Can we access your project?
Current Behavior
When I add a new Component Parameter to an existing component (String type, tried both Required and non-Required) via the pencil icon → "Add Parameter" → Confirm, a toast appears within a few seconds: "That would cause a breaking crash! The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you." The new parameter is then silently removed — the component reverts back to its original parameter list.
This happened identically 6+ times in a row, including:
This suggests the "breaking crash" detector is reverting recent project changes generally, not specifically the parameter edit — no actual layout option was changed by me when adding the parameter, so the toast message doesn't match the action taken.
Project: https://app.flutterflow.io/project/trip-mate-vbcc0n
Component affected: RequestCard (and its duplicate, RequestCardCopy)
Expected Behavior
Adding a Component Parameter should be saved normally and not trigger an unrelated "breaking crash" revert.
Steps to Reproduce
Project: https://app.flutterflow.io/project/trip-mate-vbcc0n
Component affected: RequestCard (and duplicate RequestCardCopy)
Reproducible from Blank
Bug Report Code (Required)
IT4kz8jf5YhgobxY0LrtbcdvhjosC0g6TL0Zpu0bFEggGLbrBIYMaffOblVVXbC5dGxfeFu0nTgfxvfqj/PLNvA5HAeBQYhIyM8JTQ7JTkChbLaUBaiVfW1TJJpRCXK506SnvyJdKtRacXw13WDzOvOicAzAJpDEIFQjHuabLdeK2SrDX1iXc2URm05KZDPz
Visual documentation
When clicking Confirm after adding a new Component Parameter (e.g. name: requestId, type: String) on the RequestCard component, a toast appears at the bottom of the FlutterFlow editor within a few seconds reading: "That would cause a breaking crash! The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you." Reopening the Component Parameters panel afterwards shows the new parameter is gone.
Environment
Additional Information
This bug blocks development of the join-request approval feature — I can't add the parameters needed to wire up Approve/Decline actions on the RequestCard component.