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

The only thing that worked for me to solve the same problem that everyone else in this thread had was to “Reset all changes” in the used components. This solution is frustrating because it means having to repopulate the components with content that is not part of the components library file, which takes extra time and effort.

And repopulating dozens of templates is incredibly frustrating…

I’m having this same problem. Just bought a years license for this feature and it doesn’t work…

Can you try this one ?

I tried that with no luck. I had to make a new instance of the component to get the changes.

Even if those steps for fixing the issue did work in that instance, I’m struggling to see how the feature is meant to be used if changes to the master component consistently do not propagate via the “publish changes” action.

Thanks for trying the steps. Then, could you submit a bug report detailing the steps that led to this issue? You can do so by following the link: https://help.figma.com/hc/en-us/articles/360041468234-Submit-a-bug-report?

Thanks,
Toku

I had a similar situation.

A component in the Library file was published.
Instances of that component in other Files were not updating.

It appeared that the component in the Library contained some invalid (old) Properties that were not in used anymore.

Although it appeared as if the latest changes in the Library file were published, the other files were still referring to an old version of the component from several hours ago.

Once I fixed the invalid Properties and Published the Library again, all instances of the component were properly updating in other Files as well.

Same here. Only solution is to start reset all changes and repopulate all the data. Try to fix it quickly please, this is tremendously impacting my productivity on Figma right now…
Thanks !

I have also faced this same problem and I have some thoughts on why it could happen.

We are using components built in a separate library file that we are using inside a file connected to this library.
The component (let’s call it component X) I am having problems with is using nested sub-components that are not being updated when changed. But when we make changes to the nested sub-components component X is added to the list of changed components that can be published.

The library is published and component X is updated (with changes to X) but the nested components within are still linked to an outdated variant of the sub-component.

Here are some thoughts I have that could cause this:

1. Initially, the nested components used within component X were also published but later we added a “_” prefix since they are internal sub-components that shouldn’t be stand-alone. Could it be that in making the sub-components internal (not published) Figma is gets confused and points to a previously publically available caches variant?

2. Since we have applied overrides to the properties of the nested components that later has been edited it might not take the changes due to the property changes?

2.1. We have updated the layer names of some of the texts in the nested component.
2.2 We have updated the names of the nested component set properties
2.3 We have removed some obsolete, unused properties for the nested component set.

TL;DR Maybe something is cached and then not updated when a change is published.

I hve the same problem. Tried “Repair component connection” but nothing happen.
Please fix this asap. Thanks!

Same issue here. Here is an example recording of the problem: https://youtu.be/v5wj5DOSsYE

Please fix or provide a viable solution for those of us working on large projects that apparently can’t scale.