Instance swapped icons do not receive color updates anymore

it would be great to have a quick video recording to see if we can replicate it

Screen recording on Youtube: https://youtu.be/jXXXwC2i_Xk

New demo file for the screen recording: https://www.figma.com/file/h0ih7CwsAIvwT0OLH26RDZ/Icon-swap-component-color-updates

(Also submitted a bug report through the help center, with the recording and file included.)

Hi, what is the current status on this topic?

I am working on a huge design system with an extended icon library atm. This issue ruins the whole concept.

Did anyone find a workaround other than the property feature yet?

Hey everyone,
Thanks for your patience as our engineers started their investigation.
To give you some visibility, after checking Dan_Hopewell’s case, the engineering team have marked this as a long-standing issue, not affected by recent code changes. As such, it generally takes some time for them to find the right solution and quality check it for any unexpected side effects and we’re not able to offer any firm timeline for when it will be resolved. We apologise for any inconvenience it causes in the interim. If they’re able to make a fast fix or have further information for you, we’'ll let you know right away.

Hi Celine any update on this matter? Thanks in advance.

Hi @Dan_Hopewell did you find any workaround for this? Facing the same issue in a more complex scenario with variables applied, happy to connect to find a workaround together!

@Celine_Figma

I also recently started having this issue in my components. Swapping the icon in my instances doesn’t retain the link to the main component, so if I change the icon, it no longer receives color updates from the main one. Is this not the main use case of the feature? 🙂 Currently, it makes my component system hardly beneficial for iteration.

Hi there! Unfortunately, this is a longstanding bug that our engineers are aware of and tracking.

While we unfortunately cannot provide an ETA on when this may be resolved, I can also add your case to our open bug report to hopefully give this more visibility. In the interim, the best work around we can suggest is to manually override the color again after swapping instances.

If they’re able to make a fast fix or have further information for you, we’'ll let you know right away.
If it is not the same issue, please reach out to the support team with details of your bug so our technical specialists can investigate: here Thank you for your understanding 🙏

We found a solution implementing a mask on top of the imported sub-component icon. In this way we apply the token to the mask itself, it will keep consistency across different libraries, especially in a context with multiple different libraries for a multi-brand multi-theme Design System.

Feel free to ping me in case you need help, we worked on this feature together with @Toty 👏 🔥 our Design System Ambassador for a new Business product.

The same problem is when an icon (a variant) has been changed with a help of a variable (using theme, this approach: https://www.youtube.com/watch?v=6Z3EfejbCuY). The icon picks a color from the core component on an instance locally in the library file, but not in the external file that is using this library. So annoying…

This an issue that has been there for years btw, has been talked about a lot I believe as well. Still no fix unfortunately.