Hello everyone 🙂 1 year later, I think I’m experiencing exactly the same issues as those mentioned in these topics: Resolved: Overrides not preserved when library is pushed Ask the community Hi there, I have a Design Library file in which I use to make changes to the master. I then push these to my Project file. I have never experienced issues before with pushing out changes to the project file, overrides have been preserved. However, today I am experiencing an issue where my overrides in the Project file are being wiped upon updating the library. Example steps: Library has an ‘icon’ component with lots of different icons as variants. These are all coloured red in the library f… Modifying Component Resets Overrides on Instances of that Component Ask the community Hmm alright can you reach out directly to support@figma.com. We’ll ideally need to take a look at the files to see why this might still be happening. If you can reach out and share both the library file and instances file with us, with edit access (please give edit access to support-share@figma.com) Also if you could point us to the exact instance that’s experiencing the problem and the exact overrides that are lost, that would be super helpful. Thanks Instance keeps resetting back to main component’s contents when updated Ask the community Instance keeps resetting back to main component’s contents when updated 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.

Question

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

Forum|Forum|3 years ago
December 15, 2022
17 replies
3953 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.

Ask the community

This topic has been closed for replies.

Yann_Penhouet

Hello,

we have a problem when we modify an instance of a nested component.

Indeed we have a level 1 component with different variants, which we call in a level 2 component.

We call an instance of this level 2 component, we modify for example the fill of one of the layers.
But if we ever change the level 2 (by changing the variant of the level 1 component we call), then the fill resets to match the selected variant.

Is there a solution to this problem?

Thanks

Thibaut_netatmoAuthor

Hello! I think it’s more or less the same problem I have yes…

I created this topic and made two tickets to the support in the hope that they would fix this bug soon enough.

Gregor_Pichler

Did you find a solution for this problem? Facing the exact same issue right now.

Thibaut_netatmoAuthor

Hello @Gregor_Pichler , no unfortunately I was in discussion with the Support team who were very responsive but after telling me several times that their Engineering team would look into this issue still haven’t got back to me 🙁

Price_Jared

I’m having the same issue.

E

Enes_K

I am also having this issue and recently checked with the support team. They say they are aware of the situation, this is a bug, but there is no ETA for any solutions. All we can do is to wait and expect Figma team to resolve this. Until they come up with a solution, we need to fix every single overrides manually after any library updates which means 3+ hours of labor on my side.

Morten_Larsen

New Participant

Im having the same issue

S

Sarah62

Having the same issue with designers who are using my design system files. This is increasing labor costs. Has there been any resolution on this?

Julianne_Walkiewicz

Having the same issue. Any chances to the master component result in overrides for all the custom text in our files and it’s a real problem.

Viorel1

Having the same issue, i tried to come up with some work around but unfortunate none, hope to have an answer from Figma Team soon.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO