Corrupted component instance blocks rename/delete/duplicate — persistent "Invalid Action" revert

[adamjlee55-arch]

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

Project: CamCursor (cam-cursor-x9kb70)
Page: tracking_controller

Summary

Two ControlCard component instances on this page both display the same instance name (ControlCard) in the widget tree and properties panel. This produces a build error, and every standard method for resolving the naming collision (rename, delete, duplicate page) is blocked by the editor with an "Invalid Action" message and automatically reverted.

Build error

duplicate_definition: The name 'controlCardModel' is already defined.
return_of_invalid_type_from_closure: The returned type 'ControlCard2Model' isn't returnable from a 'ControlCardModel' function, as required by the closure's context.

Expected Behavior

I expected to be able to rename, delete, or duplicate the conflicting ControlCard component instance through the standard editor actions, so that each instance on the page has a unique identifier and the app builds successfully without a duplicate_definition error.

Steps to Reproduce

1. Open the tracking_controller page and view the Widget Tree.
2. Observe two separate ControlCard component instances nested in the same Column, both showing the instance name "ControlCard" in the top "Name" field of the properties panel.
3. Run a project build — it fails with:
   duplicate_definition: The name 'controlCardModel' is already defined.
   return_of_invalid_type_from_closure: The returned type 'ControlCard2Model' isn't returnable from a 'ControlCardModel' function, as required by the closure's context.
4. To resolve the naming collision, select the second ControlCard instance in the widget tree and attempt to rename it via the "Name" field in the properties panel. Result: an "Invalid Action — The most recent action would have caused a crashing error, so we've undone it for you" message appears, and the rename is automatically reverted.
5. Attempt to rename the same instance directly from the widget tree via double-click and via right-click → same "Invalid Action" message and revert.
6. Select the second ControlCard instance and attempt to delete it via the Delete key. Same "Invalid Action" message and revert — the instance remains in the tree.
7. Attempt to delete the same instance via right-click → Delete. Same "Invalid Action" message and revert.
8. As a workaround, attempt to duplicate the entire tracking_controller page (right-click page in Pages list → Duplicate Page). Same "Invalid Action" message and revert — no duplicate page is created.
9. Perform a full browser refresh (close tab, reopen project) and re-check the widget tree — the two ControlCard instances are still present, both still named "ControlCard," confirming this is not a stale editor state issue. Project sync status shows "Synced" throughout.

For comparison: an identical duplicate-instance naming collision occurred on a different page (sensor_settings, involving SettingRow/SettingRow2 instances) and was successfully resolved there by renaming each instance via the properties panel "Name" field — that rename action was accepted without triggering the "Invalid Action" error. This suggests the issue is isolated to this specific corrupted ControlCard instance on tracking_controller, not a general limitation of the rename feature.

Reproducible from Blank

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

Bug Report Code (Required)

IT4glfLluYt1xdtJ18+BYO9aq2UUQ0N8RJc0i94bGAwaCOPrBIlzP/7BM1hoTcOndwlYL1r88X403NLJvvPpCsACAAWXUaFz1ZVXdwLJcGCtVKatOrq0QHZDO9FhCUyi1KSO2SJ+WPNzWF4W3DqqOOysdATbJZDaIEcjRv2jBLPJo3SqABzVUTtW3SwJMG7eTI5ODEz25eKMrop5yfj/0w==

Visual documentation

Environment

- FlutterFlow version: Current 7.0
- Platform:Web
- Browser name and version:Chrome Version 150.0.7871.187 (Official Build) (64-bit)
- Operating system and version affected: Windows 11 Home

Additional Information

No response

[Alezanello]

Hello!

I wasn't able to replicate this behavior. If you're still experiencing this issue in your specific project, please contact our support team through the in-app chat or by emailing support@flutterflow.io. We'll be happy to take a closer look and help you troubleshoot.

[adamjlee55-arch]

I've recorded a video of where this issue seems to start (the easiest workaround I tried) and uploaded it to Loom for you to see what's going on. Does this help at all?

https://streamable.com/ehw37r