Skip to main content
Farzona
January 18, 2023
Solved

Changes published in library are not updating component instances in other files that use the library

  • January 18, 2023
  • 69 replies
  • 17581 views

Hi there,

We have a team library with components, and other project files using instances of these components. When publishing changes to the master component in the source file (library) we stopped receiving the “Review and accept library updates” notification in other project files and obviously component instances were not updating.

Yesterday (17.01.2023), this notification was appearing but the changes were still not applied in component instances in other files.

This is an important issue, as all our work relies on the libraries working properly. Urgent help would be appreciated.

Thanks.

UPDATE: I tried solution #3 from this thread and it is still not working.

This topic has been closed for replies.
Best answer by Manuela_Mesterhazy

UPDATE ⚠️

I spoke to Figma and they figured out what happend on my end, maybe it helps some of you.

If you have variants applied to a library component, all labels must have a unique name. Figma displays a conflict error if variants have the same value, but if you have a library component and the setting labels are called the same, this conflict error is not displayed. The system recognizes it as a conflict and therefore it won’t update the component until it is fixed, so it will never show up in your updates, even if you think you have published it.

Make sure all labels in your settings are unique.

Here was my mistake to give you an example (see image attached). We have two secondary buttons in the toolbar library component. The value can be off/on, so no conflict there, but because there are two items called secondary button, the system cannot map it correctly and the “conflict” was never communicated to me, so I did not know this was the reason why my component would not update and be published.

69 replies

Thu_n_Nguy_n
July 26, 2023

I’m having the same issue here! Super frustrating!

July 26, 2023

The issue is really terrible. I can’t keep working. Please fix it

Clare
New Participant
July 27, 2023

Just happened to me too. The solution didn’t help!

July 27, 2023

Mine is also not working 😦 tried refresh, changing browser, changing to and from app, republishing and that solution and nothing has worked. Pease help!

Cynthia3
July 27, 2023

Same issue its very frustrating… The message that usually shows up saying to updates the components that have been changed in the library wont show up anymore in my design file. Can you please fix this.

July 28, 2023

Super frustrated as well, and I finally have it working again. I did two things, and I am not sure if 1 was part of the solution, so try 2 first:

  1. (desperation) I cut and pasted the entire board (CTRL-X > CTRL-V) - all elements/components etc.
  2. Click “Assets” in the side bar, click the library book icon, and you’ll get the Libraries/Updates popup. Click “Updates” on the right, and update them all.

I now get the automatic “Component updates available” popup. Hope 2 works for you as well.

July 28, 2023

I am having the same issues, basically Figma is telling me that libraries are published but once I update them in the other files, half of the components are not changed. None of the listed solutions works for me.

Janaine_Arioli
July 28, 2023

I’m having this issue too. The notification of updates on the component is showing but nothing changes on the file. Hope Figma fix this ASAP!

jbrycedavis
New Participant
July 31, 2023

Us too - getting “Publishing Successful” message, but changes aren’t applying and styles aren’t updating… I also have team members that are not getting updates from files (not even showing that there are updates to pull in) - in some cases it eventually shows up - 5 days later (literally)…

Cynthia3
August 1, 2023

I was in contact with Figma support for the past few days and it was fixed on my end, today i asked them is smt was fixed in the code by email so we’ll see. The message reappeared this morning to update the instances of a library components. I hope its back to normal for all of you as well.