Can we access your project?
Current Behavior
In the BidCard component's widget tree, opening the Button's "On Tap" Action Flow Editor (which already has 5 valid actions: Update Document, Read Document, Trigger Push Notification, Update Document, Navigate To) and clicking the "+" button after the last action, then selecting "Add Action" from the context menu, immediately triggers an orange toast saying "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 editor then navigates to a "Select Action Trigger" screen incorrectly scoped to the "BidCard" component itself instead of staying on the Button's action flow. This is 100% reproducible every time.
Expected Behavior
Clicking "+ Add Action" after the last existing action in the Button's On Tap flow should simply open the "Select Action Trigger" / "Select New Action" picker for that action slot within the Button's flow, and let me add a 6th action normally, without any crash warning and without leaving the Button's action flow context.
Steps to Reproduce
- Open the Cabby project in FlutterFlow and navigate to the "BidCard" component's widget tree.
- Select the Button widget inside BidCard, open its "On Tap" action flow (already contains 5 actions: Update Document, Read Document, Trigger Push Notification, Update Document, Navigate To).
- Click the "+" icon below the last action (Action 5: Navigate To).
- Select "Add Action" from the context menu that appears (options were: Add Action, Add Conditional, Add Loop, Add Parallel, Paste Action(s)).
- Observe: an orange "That would cause a breaking crash!" toast appears, and the editor jumps to a "Select Action Trigger" screen scoped to the BidCard component instead of adding a 6th action to the Button's On Tap flow.
Reproducible from Blank
Bug Report Code (Required)
ITEelfLlw5ZJpb0D1anQd+4w+AMzGkQ5a40/lO1Edw0dCZDoPO0Uac/7P0lWXL2oY29bKEWLgj4C7vDKj4bfGPZfAxGtb4RNzbl6ST3hcz6/aoSzDs2wZH9SMJhYfR3D37ak3B4lXPhiS3wZ202MAPCWdA7bQL36Zwh9f6PHaOI=
Visual documentation
Note: Automated image upload to this form failed repeatedly (as it did for the previous related bug report, issue #7287) - the drag-and-drop attempt returned "Failed to upload" for the file. Description of the visual evidence: a screenshot of the BidCard On Tap Action Flow Editor showing an orange toast titled "That would cause a breaking crash!" with body text "The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you.", displayed on top of a "Select Action Trigger" screen with a "Select a trigger type..." dropdown and options like On Tap, On Double Tap, On Long Press, etc. - this is the wrong context, since the flow being edited was the Button's "On Tap" action list, not a fresh action trigger for the whole BidCard component. I'm happy to attach the actual screenshot image manually if a maintainer follows up on the issue.
Environment
- FlutterFlow version: latest available (as of July 2026)
- Platform: Web
- Browser name and version: Chrome
- Operating system and version affected: N/A (issue occurs in the web-based FlutterFlow builder itself, not platform-specific)
Additional Information
This blocks basic maintenance of the BidCard component (adding actions to the bidding flow, which is core to how the taxi price-comparison app works), and is needed before we can ship the app to the App Store. It appears related to a broader pattern we've also reported in issue #7287 (Read Document reference showing "Unknown"), where the Action Flow Editor misbehaves for this project.
Can we access your project?
Current Behavior
In the BidCard component's widget tree, opening the Button's "On Tap" Action Flow Editor (which already has 5 valid actions: Update Document, Read Document, Trigger Push Notification, Update Document, Navigate To) and clicking the "+" button after the last action, then selecting "Add Action" from the context menu, immediately triggers an orange toast saying "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 editor then navigates to a "Select Action Trigger" screen incorrectly scoped to the "BidCard" component itself instead of staying on the Button's action flow. This is 100% reproducible every time.
Expected Behavior
Clicking "+ Add Action" after the last existing action in the Button's On Tap flow should simply open the "Select Action Trigger" / "Select New Action" picker for that action slot within the Button's flow, and let me add a 6th action normally, without any crash warning and without leaving the Button's action flow context.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
ITEelfLlw5ZJpb0D1anQd+4w+AMzGkQ5a40/lO1Edw0dCZDoPO0Uac/7P0lWXL2oY29bKEWLgj4C7vDKj4bfGPZfAxGtb4RNzbl6ST3hcz6/aoSzDs2wZH9SMJhYfR3D37ak3B4lXPhiS3wZ202MAPCWdA7bQL36Zwh9f6PHaOI=
Visual documentation
Note: Automated image upload to this form failed repeatedly (as it did for the previous related bug report, issue #7287) - the drag-and-drop attempt returned "Failed to upload" for the file. Description of the visual evidence: a screenshot of the BidCard On Tap Action Flow Editor showing an orange toast titled "That would cause a breaking crash!" with body text "The layout option you selected would have caused a Flutter layout conflict and crashed your app, so we've reverted it for you.", displayed on top of a "Select Action Trigger" screen with a "Select a trigger type..." dropdown and options like On Tap, On Double Tap, On Long Press, etc. - this is the wrong context, since the flow being edited was the Button's "On Tap" action list, not a fresh action trigger for the whole BidCard component. I'm happy to attach the actual screenshot image manually if a maintainer follows up on the issue.
Environment
Additional Information
This blocks basic maintenance of the BidCard component (adding actions to the bidding flow, which is core to how the taxi price-comparison app works), and is needed before we can ship the app to the App Store. It appears related to a broader pattern we've also reported in issue #7287 (Read Document reference showing "Unknown"), where the Action Flow Editor misbehaves for this project.