Variables don't apply or update in swapped instances anymore

Ask the community
, ,
1

I’m working on a design system and encountered a bug thats slowing me 10x.

To begin with, when I swap a component with a variable property within a larger component/variant instance and then change the variable color in the parent component, the color doesn’t update in the overridden instances with swapped components. (Check out the video example)

For example in this case, when I duplicate the [Documentation/Feature Icon] component, which has an icon swap property, and swap the icon in the duplicated instance, the color gets inherited from the parent component. But when I change the color in the parent component, the color of the swapped icons in the instances remains unchanged.

Is’nt this a common practice (or at least used to), is anyone experiencing this?
I just noticed, this issue is happening across all my projects, though it worked fine last week.
Any ideas on how to fix it?

The worst part is imagine you’re designing atomic elements and creating pages using nested component instances cooperating swaps . After many iterations, you want to assign a new color to the parent component’s icon with swap property, and the new color does not apply accordingly to the instances with already swapped icon components.

2

Hi there,

Thanks for reaching out. I’m checking with our internal team. I will get back to you when I have anything I can share with you.

Thanks for your patience.
Toku

1 Like
4

Hi @Alx,m

Thank you for waiting. I’ve checked with our internal team, and the behavior of the video recording appears to be as expected. However, it might depend on factors such as layer hierarchy or naming conventions. It is curious that it worked differently last week. If your setup is the same as last week, where the swapped instances change color when the original component’s variable color is changed, could you please share the file link with access to support-share@figma.com? This won’t affect your billing. We hope to investigate this further.

Thanks,
Toku

5

Hi @y_toku

Thank you for responding, however after looking into forum I found another thread about the same issue, and I think there is misunderstanding since there are others having same issue here :

and your colleague here said that “It is bug that our engineers are aware”

So right now I am really confused how it was a common practice before, and you mentioned it did not exist ? Currently, this is not happening in any of my projects …