Hidden stale on_primary, on_secondary, and on_error theme references block Run/Test

[queenglamazon-lab]

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

Current Behavior

My FlutterFlow project is currently blocked from Run/Test by 12 Widget Configuration errors referencing theme colors that do not exist:

on_primary
on_secondary
on_error

Examples include:

Widget references theme color "on_primary" that does not exist.

Widget references theme color "on_secondary" that does not exist.

Widget references theme color "on_error" that does not exist.

All unrelated action-flow errors have already been corrected. These 12 theme-reference errors are the only remaining blocking errors.

The affected UI includes a reusable Button component inside a LocationSearchSelector component that was originally created using FlutterFlow's AI/Designer component-generation functionality.

When I click an on_primary validation error, FlutterFlow navigates to an internal Icon inside the reusable Button component. However, the visible configuration does NOT reference on_primary.

The visible Icon configuration is driven by a component parameter, and the Button instance shows a valid existing theme color such as Primary Text.

I have also inspected the reusable Button component and its exposed parameters. They show valid current colors rather than the missing snake-case theme colors.

Changing the Icon's UI Builder Display Value to #FFFFFF does not affect validation. The error count remains 12.

I also attempted to create custom colors named:

on_primary
on_secondary
on_error

FlutterFlow automatically removes the underscores and creates:

onprimary
onsecondary
onerror

As a result, the missing snake-case references cannot be recreated through the visual Theme interface, and the validation errors remain.

This appears to be a hidden/stale project metadata reference rather than a visible widget configuration problem.

It appears related to previously reported FlutterFlow issues involving Designer-generated components and phantom on_primary theme references.

Expected Behavior

Expected Behavior

Widgets/components whose visible properties reference valid existing FlutterFlow theme colors should not fail project validation because of inaccessible or stale theme-color IDs stored in hidden project metadata.

If on_primary, on_secondary, and on_error are no longer valid theme colors, FlutterFlow should either:

migrate those references to valid theme colors,
expose the references in the Builder so they can be corrected, or
remove stale references that are no longer used.

The project should then pass validation and allow Run/Test without requiring the affected component to be rebuilt.

Steps to Reproduce

Steps to Reproduce
Open the existing FlutterFlow project.
Run project validation or attempt Run/Test.
Observe 12 Widget Configuration errors involving on_primary, on_secondary, and on_error.
Click an on_primary error.
FlutterFlow navigates to an Icon within a reusable Button component.
Inspect the visible Icon/Button/component color properties.
Observe that the exposed property uses a valid current FlutterFlow color rather than on_primary.
Change the UI Builder Display Value to #FFFFFF.
Re-run validation.
Observe that the error remains and the total remains 12.
Attempt to create a custom color named on_primary.
Observe that FlutterFlow changes the name to onprimary.
Repeat for on_secondary and on_error.
Re-run validation.
Observe that all 12 hidden-reference errors remain.

Reproducible from Blank

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

Bug Report Code (Required)

IT8wl8/q24lgrsNc15PiafowmSQXJkw2aOcr0uxuWRAgfY/qPI13PeHOR1ZuOPbnYXNUOkamgk8ypq2PhePLF/k3GxuWf61x+ql1FgLKe2qyRIyrCai7P3QmGdFRGFSh0MGvpxN+BLN2LngfxWO6Gty9bA/UCYzYDm1MG/yKCLzIjV6cFR/dOxZvzSc/H2bTPvM1ZVDq+f6QspZl1eTjzw==

Visual documentation

n/a

Environment

- FluttEnvironment
Platform: FlutterFlow Web
Browser: Google Chrome
Operating System: Windows
FlutterFlow version: Please derive from the Bug Report Code/project if available.erFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

Additional Information

Please inspect the project's underlying metadata/configuration for stale references to:

on_primary
on_secondary
on_error

The visible Builder configuration has already been checked repeatedly and does not expose these invalid references.

Please do not treat this as simply a missing color-selection issue. The FlutterFlow interface prevents recreating the exact snake-case IDs because underscores are stripped from custom color names.

The affected component also contains working application logic that I do not want to rebuild merely to remove inaccessible metadata.

A metadata cleanup/migration that preserves the component and its existing actions is preferred.

[Juansarmi]

Hello!

I'm sorry you're experiencing this issue.

Based on Flutter and FlutterFlow naming conventions, I strongly recommend using camelCase when naming classes, functions, and custom colors to help avoid issues like this. In fact, it should not be possible to include an underscore (_) in the name of a custom color.

I'm sharing a similar issue that was previously resolved, where the user fixed the problem by renaming their custom colors. After doing so, they were able to resolve the project issues and continue developing their app → #7093

If you continue to experience this problem, I recommend contacting Support through the in-app chat or by email at support@flutterflow.io.

Best regards.