Skip to main content
Thibaut_netatmo
December 15, 2022
Question

Nested variant instances within a component are reset after the library update?

  • December 15, 2022
  • 17 replies
  • 3952 views

Hello everyone 🙂

1 year later, I think I’m experiencing exactly the same issues as those mentioned in these topics:

Unfortunately, the solution suggested in the related topics I mentioned above — reload Figma and run “Fix instance overrides” from the Quick Actions — is outdated and no longer exists.

If there a new solution?

if I may summarise the issue:

When we nest a variant instance within a component, use that component in another file and select a different variant value than the one defined by default, then every change related to that component published from the library and updated in the other file will reset the modified variant instance within it.

Here is a video I made to make it as clear as possible ↓


Please let me know if any of you are also affected by this issue.

If my example only shows a reset of the variant name, be aware that this issue affects all possible overrides making it much more annoying with more complex real components!
To me, this looks like a bug that needs to be fixed quickly.

Thanks very much.

This topic has been closed for replies.

17 replies

Rudel
September 6, 2023

Same here, annoying 🫠

Harald1
New Member
October 24, 2023

Same issue, all my level 1 components were reset after library push 😪 This is a big problem!

Thibaut_netatmo
October 25, 2023

OK Figma Support, it would be good to take a serious look at this problem from now on. I haven’t heard from you since…

I even have the feel that this issue of embedded components being reset applies to the same file now, and not just when you use the component in another file after updating the library…

Kemppainen_Mikko
New Member
December 13, 2023

This is a considerable issue in our company as well. Any updates on this one Figma Support?

Richard_Earney1
March 25, 2024

Likewise this is causing a lot of wasted time, resetting icons in files when a Library update is pushed.
And fix ETA @support_team

djv
Figmate
Community Support
March 26, 2024

Hey All, sorry for the trouble and frustration!

Usually, this occurs when an update made to the main component alters the component structure, hierarchy, or layer names.

These types of changes prevent overrides from being preserved as described here: Apply overrides to instances.

As a first step, we recommend comparing the component instance before updating with the latest component version to check if any recent changes:

  • Added or removed any component variant properties
  • Switched any nested components to a different variant
  • Added or removed component sublayers
  • Renamed any component sublayers

If none of these help, our team can take a closer look at why the nested instances are resetting. If so, please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new

Be sure to use your Figma account email, include a link to the file, and share it with support-share@figma.com.

FYI - Figma does not own Support_Team, so there is no need to tag them in the future.

George_B1
New Participant
November 24, 2024

any fix here?
This issue occurs more and more. I had it happen to a CTA where I changed only the fill color to a variant…that was it…and it reset the text to default after updating the component