"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.

This just happened.

We were using slot beta. The library file has slots in the component, and now when we publishing the library, the slots revert back to normal container in the other files, and shows component error.The file updates resets tons of designs we already laid out!

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. 

Having the same problem.  When I place a child of a slotted component in a design file, the slot is just showing up as a regular frame.  

However, if I create a child of the slotted component within my design system file, copy it, then paste it into the external design file, the slot is showing up properly. 

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.