Skip to main content

We’re experiencing a random problem with component overrides in our design system which consists of multiple library files. Our components use an atomic structure, where small individual components are combined (sometimes with overrides) to create larger components.


The problem we’re facing

We’re using some components in a design file and they have overrides applied to them. When a new library update is published, taking the new updates in the design file breaks our overrides. The component properties/variant selection is intact, even the value of the overrides are intact, however the instance would either loose border radius, or have its alignment changed or the layer name resets to the original name from the atomic component. This happens to some specific components, and not others. And this also happens randomly, sometimes some components break, while others don’t.


We tried recreating the whole library from scratch with a few components to see if the problem persists, and unfortunately the instances still break.


Here’s an example of a list component that has a logo element which breaks on a new publish:


If you inspect the broken instance, you can see that the border radius has gone to zero. After toggling something back and forth from the component properties, the original value comes back.


I’ve created a detailed screen recording along with commentary showcasing this problem happening on a particular logo element: View screen recording


We’ve tried a lot of things and nothing seems to be working, so our assumption is that it might just be a bug. Is there something in the way the component is built that is breaking it? Or perhaps this is a known bug?

Any support will be appreciated. I’m happy to share more details needed to investigate this issue.

(I’ve shown this in the screen recording, but sharing it again as screenshots)


Here’s how the library files are structured:


And here is the components file:


I feel your pain – we have the same issue all over sudden. If I click on the broken layers, they jump back to correct, but as soon as I close the file and reopen it, it is back to corrupt.


I’m having exactly the same issue. Is there a fix for this?


I have this issue too


We are having a similar issue.


Here are the steps to reproduce this ( please see photos )




  • base component with 2 variants, a text property for the label is defined




  • parent 1 has an instance of base component




  • parent 2 has 2 instances of parent 1




  • change the text of the 2 instances in parent 2




  • change the variant of one of the instances in parent 2, the text override is maintained.




  • change the variant of Parent 1




  • the text override in the Parent 2 instances is reset if you change the Parent 2 instance’s variant, but sometimes, it does not




  • if you keep changing the Parent 2 instance’s variant and change the Parent 1 variant, eventually it will reset the Parent 2 instance’s text override





Just FYI, exposing properties from nested instanced in Parent 1 does not solve this issue either.

This issue started I think < 6 months ago, prior to that, this issue did not exist.

We could change the Cell width variant that was nested inside a default table row and it would completely preserve the text override and / or component swap inside the Cell


The same issue

image


Hey Dmytro,

Sorry to hear you are having issue with the component overrides. It’d be great if we could have a copy of your file, and a quick video recording when you are trying to publish the library. It will help us to try to replicate, please fill out the form here: https://help.figma.com/hc/en-us/requests/new

Be sure to use your Figma account email, include links to the file, and share it with support-share@figma.com so they can take a closer look.


Had the same issue today. Fixed by copying the entire page, pasting it, then deleting the original (broken) screens. Tested with multiple users refreshing Figma, closing Figma, etc, seems to be working fine now.


I have the same problem and it’s in my DS file. All my components are broken now…

I have to click on it and the component fixs itself but when i refresh (not event publishing) it comes back to the broken state…

I cant copy the entire page and deleting the original i will loose all my links…

Plz help 😱


Hey there; any updates on this @Celine_Figma?


When doing this, did the component in your copy/paste get updated by the updated library publish or no?


We are facing a similar issue when publishing library updates, some components are reset to default values. My assumption is that this may be occurring due to slight format changes.


That said, has anyone figured out any process or solutions to mitigate this or if there if any guidance in how to avoid moving forward?


Hi everyone, thanks for flagging it.

I’ve checked in our backend, and we have a similar bug that has been fixed in 2023. I also checked the support ticket of @ahmad_tabby , it seems that the issue has been fixed on its own.


This may be a regression, but it’s hard to tell without investigating further the root cause of your issue on your end.

For others, if you are still encountering the issue, please reach out directly to the support team so we can investigate it further with a copy of your file and we can try to replicate it. As mentioned, please fill out this form: here

Be sure to use your Figma account email, include the URL of the file, and share it with support-share@figma.com as an Editor so they can take a closer look.


Thank you 🙏


It happenes all the time to our team. When you click they reset to the correct properties and positions and once you restart they are broken again.


The funny thing is that a colleague of mine sees it fixed but when I open it on my machine it’s broken.



I even tried duplicating the artboard to try a fix suggested here. I saw it ok but my colleague broken. I think it has something to do with updating library inside a file, because it happenes when we update the library in a file. Also I noticed that my colleague had no update for the file but I see the Library update that I need to do, which is really strange having the fact an update is on a file level not on user level.


Edit:


I had unaffected file. I had library changes so I clicked Update on all pages. The Figma file froze so I had to close it. After reopening it it was updated and all components broken. Now another file of ours is basically unusable


Reply