Skip to main content
Solved

Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer

  • July 21, 2026
  • 16 replies
  • 169 views

mark.braithwaite

Variant layer names in the format Prop=Value (e.g., State=Selected) work correctly and are reflected in the "Current variant" panel. However, simply clicking into the layer name field to select/focus it — with no actual edit — and then clicking away causes Figma to throw:

"This layer has an invalid name. Make sure that all variant names are of the form: Prop=Value, Prop=Value, …"

After this happens, the "Current variant" panel's State dropdown shows "—" (empty/unset) instead of the correct value.

Steps to reproduce:

  1. Open a component set with a variant layer named in valid format, e.g., State=Selected (property recognized correctly, shown in Current variant panel as State: Selected).
  2. Click on the layer name in the Layers panel to select/focus it (do not type or change anything).
  3. Click away, back onto the canvas.
  4. Error appears: "This layer has an invalid name…" and the Current variant panel now shows State: "—".

Expected behavior:
Clicking into a layer name field without making changes should not alter or invalidate the variant property.

Actual behavior:
The act of focusing (and possibly blurring) the name field alone is enough to break the variant parsing — no text change required.

Notes / things to check:

  • Suggests the name field's blur/commit handler may be re-serializing or re-validating the name incorrectly, stripping or misreading the Prop=Value structure even when untouched.
  • Confirmed happening on a single-property variant (State=Selected), so this isn't limited to multi-property names like State=Default, Color=Blue.

Best answer by Celyn_L

Hi everyone, Celyn here. I work closely with ​@Tom Reem.

Our Engineering team has pushed a fix and confirmed that the issue has been resolved. Please refresh your files and let us know if you’re still experiencing any issues.

Thanks again for reporting this and for your patience while we worked on getting it resolved!

 

16 replies

M.ant
  • New Member
  • July 21, 2026

I seem to be having issues when naming my variants in the layers panel.

When I check my variants, the properties on the right panel, appears as normal.
Then if I click on my variants in the layer panel and go to rename the layer, the properties get striped of it’s definer and anything that has an “=” before it is removed.

This then causes Figma to tell me there are invalid layer names but that’s because it’s been stripped out.

Can somebody help please? Video attached
Figma Desktop App version 126.7.6

[Moderator note: This post was merged from Variant Naming Error Bug into Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer on 21-Jul-2026.]


Gabriel Marquis-Angulo

Hello Figma Support team,

We are experiencing a critical bug affecting our component variants. We have thoroughly checked our file's version history: absolutely nobody in our team has manually touched or modified the layer names, yet the system corrupted them automatically.

Key Issues:

  1. Automated Name Corruption: Our variant layer names, which were previously formatted correctly using the strict key-value code syntax (e.g., Type=x, State=x), have spontaneously changed into plain comma-separated lists (e.g., Weak, Default, Regular).
  2. Breaking UI Interaction: The critical breaking point happens in the left Layers panel. When a designer simply clicks on the purple variant diamond icon/layer name, it immediately breaks the applied component properties. The text turns completely plain black, the component logic detaches, and Figma throws the "Component variant – layer has invalid name" error in the right sidebar.

This is a severe regression. The interface is forcing a text-breaking action upon a simple click navigation, and Figma itself altered our library's original underlying syntax without user input.
 

Steps to reproduce:

  1. Open the file and notice that layer strings have shifted on their own from Property=Value syntax to plain commas. e.g, Default,Regular
  2. Click or double-click the purple variant diamond icon in the left Layers tree.
  3. Observe the layout link immediately breaking, turning the text black and destroying the applied properties panel structure.

Please look into this regression as it is currently disrupting our production team.

This is a new bug and we’ve seen couple of topic about it. 

Thank you,
Gab!

[Moderator note: This post was merged from “Component variant layers spontaneously losing formatting and turning black / "layer has invalid name" bug” into "Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer" on 21-Jul-2026.]
 

 

 


Gabriel Marquis-Angulo

My colleagues and I are having the same problem. We're waiting for a response from Figma!

[Moderator note: This post was merged from Variant Naming Error Bug into Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer on 21-Jul-2026.]


Jaycee Lewis
Figmate

Hi, ​@mark.braithwaite 👋 Thanks for the detailed write-up — the repro steps and the note that it fires on a single-property name too are really helpful.

Two details to shore up:

  • Which Figma version are you on, and is this the desktop app or the browser? (You'll find the version under the Figma menu → Help and account, or in-browser via the same menu.)
  • Does the same thing happen on a brand-new component set you build from scratch in a fresh file — or only on this existing set?

In the meantime, one reliable way to avoid the layer-name commit path entirely: edit properties and values from the right sidebar rather than the Layers panel. Figma actually recommends the sidebar over renaming in the layer name for exactly this kind of parsing friction — details here under "Fix corrupted variant errors"

If you're able to share a short screen recording of the focus-and-click-away sequence, that will be very helpful in triaging. Thank you! — Jaycee


mark.braithwaite

Thanks, Jaycee. Really struggling with this.

  • Figma Desktop App version 126.7.6
  • Occurring in both the desktop app and browser, on multiple computers.
  • Started around 3pm (PST) yesterday.
  • Reproduces on a brand-new component set in a fresh file too — not specific to the original file.
  • Tried on my wife's Figma account and did not see the issue. Tried on my coworker's account today and did see it. Seems tied to something at the account or environment level rather than the file itself.

Steps to reproduce:

  1. Create a component, add a variant — first instance labels as "Default," second as "Variant2."
  2. Rename the property/value via the right-side palette (e.g., property → "Color," value → "Red"). Layer name updates correctly to "Color=Red."
     

     

  3. Select "Variant2," add a second value from the palette (e.g., "Blue"). Works as expected.
  4. Click back on the first variant's layer name — instead of "Color=Red," it  shows just "Red."
     

     

  5. At this point, the instance has unbound from the component.
     

     

Happy to put together a screen recording if that would help.

Mark


Jason_Burns
  • New Member
  • July 21, 2026

Running into the same issue these past 24hrs


mark.braithwaite

Jaycee. Here’s a screen capture...


M.ant
  • New Member
  • July 21, 2026

Having the same issues and I’ve seen a few posts like this now


Mark Braithwaite

you are not alone: 

[Moderator note: This post was merged from Variant Naming Error Bug into Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer on 21-Jul-2026.]


Tom Reem
Figmate
  • Figmate
  • July 21, 2026

Hey ​@Gabriel Marquis-Angulo — thanks for the detailed write-up and the clear reproduction steps. You're right that others have reported this, so I've merged your thread into the one where we're tracking it. Further updates will land here.


Tom Reem
Figmate
  • Figmate
  • July 21, 2026

Hi ​@M.ant and ​@Mark Braithwaite — thanks for the reports, and for providing the video. I’ve merged your posts into this thread so we can track this issue in one place. We've flagged this to our Technical Quality team to investigate, and we'll post updates here as they come.


Tom Reem
Figmate
  • Figmate
  • July 21, 2026

Update: The Technical Quality team escalated this to Engineering, who's now working on a fix. We'll post here as soon as it's deployed.

Thanks again for the reports, and for your patience as we work on a resolution.


Celyn_L
Figmate
  • Figmate
  • Answer
  • July 22, 2026

Hi everyone, Celyn here. I work closely with ​@Tom Reem.

Our Engineering team has pushed a fix and confirmed that the issue has been resolved. Please refresh your files and let us know if you’re still experiencing any issues.

Thanks again for reporting this and for your patience while we worked on getting it resolved!

 


mark.braithwaite

@Celyn_L ​@Tom Reem first glance seems to be working, though variant layer names now contain the entire string, even if I create a new component. No sure what impact that has other than not being convenient. 

 

 


Celyn_L
Figmate
  • Figmate
  • July 22, 2026

Hi ​@mark.braithwaite, thanks for confirming that the original issue appears to be resolved, and I appreciate you calling out this behavior.

I'm checking with the team to confirm whether the variant layer names displaying the full property string is expected and I'll share an update here as soon as I hear back.

Thanks again for flagging it!


Tom Reem
Figmate
  • Figmate
  • July 22, 2026

Hi everyone, back with an update!

I checked in with the Engineering team and confirmed that the variant layer name behavior ​@mark.braithwaite described here is being tracked as a separate issue.

We can't share a specific timeline for a resolution yet, but the fix is under review. We'll post updates here as we learn more.