"Properties and values of this variant are conflicting" - but they are not

Working through adding slots to our design system. We previously had a card component that has many variants (outline, floating, hover, selected, etc) and inside that card we had an instance swap component. Using the new wrap in slot feature, we noticed that when we swap variants on an instance of the card component, anything within the instance swap component would transition between our variants of the main card component but anything outside of that (in the slot) would only appear in the single variant. I believe this is due to the fact that slots need unique names in each of the variants since they are treated as individual properties. Is there anyway to get around this or maybe something that can be added soon? I attempted to name all of the slots the same name in the component variants but won’t let me publish since it has conflicting property names. Thanks!

I’m having the same issue, the workaround I found was to create a component that has just a slot in it then nest that component into my card component that handles the various states I have. I don’t like this because I can’t edit the auto layout flow of the nested slot component and it feels like a hack. So I will be holding off for now incorporating slots in our component libraries.

Having a similar issue.  We have a menu option component with an instance swap to add a chip, icon, badge, button etc to the right beside the text.  Replaced the instance swap with a slot.  It works completely fine within my component library file, and even lets me publish the component.  

But when I add a child of this component to any of my design files, I get a property conflict error.  This error only exists in children placed in external design files, but does not show up on the parent component or children of it within my design system file. 

We have a menu option component with an instance swap to add a chip, icon, badge, button etc to the right beside the text.  Replaced the instance swap with a slot.  It works completely fine within my component library file, and even lets me publish the component.  

But when I add a child of this component to any of my design files, I get a property conflict error.  This error only exists in children placed in external design files, but does not show up on the parent component or children of it within my design system file. 

I've been having this issue since today when I update a component and try to use it in another file.

Good to know it’s not just me! Hopefully they fix this soon because it’s preventing me from finishing a project. 

I suddenly have one of my components that, even though it will publish just fine from the design system document, errors out and won’t let me set any properties when being added to another document. I’m getting an

The properties and values of this variant are conflicting. Change the applied values on this variant to resolve this.

error message. But only when trying to use it in other files. Inserting an instance within my design system document works just fine, and there aren’t, as far as I can tell, any conflicting values or properties.

I’m incredibly stumped on what the actual problem is here and why it magically appears only in secondary files. (And, in general, it would be awfully nice if these error messages could give some additional information on what the actual conflicting values are.)

I’ve reverted to an earlier version of the design system from the history and seem to have escaped this problem.

That means I can narrow the problem down to starting when I added a specific variant of the component, but the surprising thing is that I had already tried deleting that variant (since I suspected that had been the problem) and that did nothing to remove this problem or allow access to the properties on the instances (even though the I-guess-conflicting variant had been removed).

It seems like the only solution was to roll back to a version of the component that had never had that variant at all.

So happy to see I’m not the only one.  Even when I roll back to the previously published versions of my library, the error is still there.  It has completely blocked my team’s work today

I can’t for the life of me figure out why I’m getting this error message on an instance of a component that works locally in the library file but when I pull it in as in instance in a file linking it I get the error. "The properties and values of this variant are conflicting." I haven’t changed the properties since I just instantiated it and I have no ability to change them because of the error. I went and checked the component and redid the properties several times and published and updated the library change from the design file. 

I dont know if this is a clue but I changed the properties to all booleans from a single property with 3 different values and a single boolean. Could it be there’s a ghost property that’s causing the conflict? 

How do I resolve this issue?

THIS IS DRIVING ME INSANE!!! Happening to mine too I can not figure out why; they were not broken before slots updates and i havent made changes and now they are broken

Same issue for me!!! its driving me nuts nothing changed and now all of a sudden this is happening  (the only thing that changed was slots) 

Having this same issue today. Glad im not the only one

For my design library of components, any time I add a new variant the root component is breaking in all instances. I can use the component in my Library file and it functions. When I take that component and its variants and duplicate them exactly as-is as a new component, it will work. This unfortunately means that any time I make an update (such as adding a filled version of an icon), everything breaks and I need to create a duplicate one from the original in order for me to make this work.

This certainly seems like a bug as in the Main Component we are seeing no errors. We are able to copy and paste the exact main component and use that without issue. There is something likely out of sync here between the instance and the main component, and this certainly seems like a software bug.

The attached images show the duplicate components in the file. They are 100% identical as the Menu Item 2 was simply a copy and paste of Menu Item. In the file we can see the error showing when it’s set to Menu Item, and no error when set to Menu Item 2. This issue just arose today for me.

Reporting same issue. Working fine in the morning. Suddenly started having this same issue.

After looking at this error some more, it seems like the error is happening to any text string or component swap property.  Unfortunately, almost every component in our library has those.

This bug has stopped our Figma work for the day.

When on a master component,  Slot won’t show up as a property in the + properties section on the right panel (I only see from Variant to Instance swap options) and neither when right clicking inside the nested frame in that component.

I have already tried to reload/restart figma multiple times

Same issue! 

Currently experiencing the same bug!

Having this issue too. I just added a new variant to a table component and it’s throwing this error now even though there are no conflict. It works perfectly fine inside the design system file where it’s located but throws the error when used in any other file.

Same bug, I kept trying to rebuild my component thinking I was crazy!

Also experiencing this issue.

Wait help I am having this exact same issue. 

Same issue, this is realy messing up my work dayyy