Solved

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

Forum|Forum|3 years ago
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.

Ask the community

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.

Show previous replies

Jason_Early1

I had some errors in the components that needed to be addressed. After resolving the errors it published and was updated across the files.

Alexandre_Schrammel1

New Member

I still have these problems from once in a while… I wasted a day trying to fix it since it blocks me from progressing in the work.

Manuela_MesterhazyAnswer

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.

Svetlana_Yeromenko

Thank you! This helped me with publishing an update in library 👍

In my case my work-file still didn’t suggest an update popup - so it seemed to be needed to relink the compoment instanses in work-file artboards - then it worked.

(JFI: maybe it will be usefull for somebody for relinking the component. I additionally updated the name of the main component before relink (just added some dot at the end) - thus I could see on the sidebar by the the name the difference and check which component is updated (or not). Seems like Figma in the work-file finally got this difference as well 😉

Jens_Brandt

For some time now I have not been able to update my design files that use the shared library. No updates are displayed. All the suggested solutions have not helped me out of this big problem 😦 Maybe this is a temporary technical issue.

Jens_Brandt

Maybe this is the reason today, found it on the status page https://status.figma.com/

On August 25, 2023, Figma will be undergoing scheduled maintenance, starting at 4:00PM PDT/21:00 UTC. We are scheduling the maintenance window for 30 minutes, but anticipate Figma to be unavailable for only a few minutes.

During the maintenance period, while you will not be able to open new files or refresh existing files, you can continue to work on any files that are already open. When the maintenance is over, your work should sync as expected.

If you continue to work during this period we suggest also backing up your work by saving your File locally as a .fig file. This way, if there are any unforeseen issues, you can import your saved version and continue as normal.

We hope this will not be too much of a disruption and appreciate your understanding. If you have other questions or concerns please email support@figma.com or contact us inside the app.

Harmony

New Member

I’m currently having this issue and found a hack to fix it. If I place a new instance of the component from the asset panel, I get the update notification and the subsequent instance updates. This isn’t helpful for all the other designers working with our library, however. I’m working on an emerging design system and we need to be able to trust that our assets are updating reliably!

C

candace1

I’m having the same issue. Having hacks is fine, but those fixes are not a long-term solution for teams working with shared libraries and projects.

M

Michael_Swarts

I have the issue as well. New instances show the updates in the master components. Old instances do not. In my case, a boolean property is not showing up for the old instances, even though they point to the master component, which has the property. None of the mentioned solutions worked for me.

Josh_Chambers

New Member

Same issue. Super frustrating. Grinds the work to a halt.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO