Skip to main content

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 file (original component definition)

  • I’ve used many icons in the Project file where. I’ve overridden the colour of the icon

  • I added a new icon variant within this component in the Library file

  • Published the change

  • Updated the library in the Project file


Expected result (and previous behaviour):



  • All icons remain in their selected colours in the Project file, but I can optionally switch the variant to the added icon


Actual result:



  • Upon updating the library, all icons in my Project file have reverted to red colouring (have lost my colour overrides)


Other overrides have been lost too, but have used the above as an example.


Can you please advise what’s happening here and if there are any workarounds? Unfortunately it’s not going to be manageable for me to redo every override that I’ve made after each push.


Thanks,

Audrey

I’m experiencing the same. This has reset all our work 🤦🏼‍♂️


You can try to jump back in version history or just cmd z. This worked for me and I hope I can sit this out until publishing works again 🫣


Same issue, I can’t work like this, I hope this will be fixed soon!


I’m in your team, guys 😅 Waiting for fix 🤯


Same here! Please, fix this bug!! 😭


I’m having the same issue. Not sure what’s happening, but it was working fine a couple days ago.


Same issue here – really annoying since I’m working on an important deadline


Same here! It resets all overrides, text, colors, icons…


I’ve just tested it, by creating a new library and file. It’s working fine. But if I use the library I was using before, it keeps reseting to the default state 😔

If I can’t fix it, I will need to create my whole library from scratch. Seems to have some kind of error or something that keeps breaking the instances. So frustrating!


Update: I’ve managed to revert both files (library and my working file) to yesterday’s version (through version history). Hopefully it’s working now, but I’ll have to redo what I’ve done this morning - but at least for now it seems to not be overriding my instances.


Same shit here! Thought it was our fault but it has no sense at all, our component structure is correct, checked it. @anon21722796 please check this issue asap.


Same issue!! I knew something strange was happening with Figma, I’ve been updating overrides in my projects all morning over and over again 🤯😩😥


I hope it get fixed soon 🙏


Hi


I’m experiencing a situation I’m not really sure how to explain since it feels so complex I can’t even find words for it. I wish there was a way I can get into a chat with Figma or somebody who can see directly what the issue might be… it feels… nightmarish.


My file setup is the following: I have a library file and a product file.

The library file is where all my components are and the product file contains all the flows our product has.


Today, I noticed something weird within my product file. Components were reset to their default state for no reason and I had not done anything to trigger that.


This presented me with 2 options:



  1. Use lots of hours to try and adjust reset states to custom states (we’re building a complex product)

  2. Replace Figma files with backup files from the day before where everything was working just fine (I download all files everyday as a backup for situations like this)


I started with option no. 1 but I could see that all components across the whole product were reset which would require perhaps a full day or two of manual mindless work. So I took option no. 2


I replaced my Figma files (product file and library file) with the backup files I have. At first, both files looked perfectly fine. But then I had to connect them together so the product file receives updates from the library file. When I attempted to do that, I saw that a library was missing and I had to replace it with the new (backup) file. I did that.


And then this is where weird things began happening.

Buttons text on the product file would be a different color even though it’s specified in the library. Whole product page designs would swap to other product page designs. Shadows would be missing etc etc etc.


And now I just have no clue how to fix this as it does not make any sense to me and the errors I’m getting do not have anything to do with logic.


PLEASE help!


Yes please 🙏


Great idea. Thanks, @Lea_Delazer1


Same here 👋


Same here…


I’m having the same issue.


Experiencing the exact same issue as everyone else. We can not work until it is fixed. 😭


Hey everyone, we’re aware of this is issue, and are actively investigating. To help us figure out what might be causing this if you could share file access with our team that would be great.


To do this please give edit access to support-share@figma.com for both the library file and the subscribing file.


Thanks


Josh I can give you access, but I think that this is a general issue, there’s a lot of users with the same problem.


Yup we’re aware that it’s widespread but need some help tracking down the issue and getting more information. Give access to the files can help.


@Josh


Do it yourself (simple)



  1. Library file - Create 2 button variants (active, default) - publish

  2. Subscribing file - pull the component, change the text

  3. Library file - increase the padding of both the variants - publish

  4. Subscribing file - pull updates - BOOOM - resets everything to all the instances.


Working for DHL, so I can´t give you guys any access to this.


But I can tell you this issue just killed the active release. I backrolled to an older version, but this made even more issues, by overwriting also other instances with the component content.


About 30 people can´t work right now …


In my case I have a library file with a set of components, if any of the component properties are changed and updates are pushed I get text values overrides reset in the file where that component is used.