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 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 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.

After working with the excellent Figma support team I learned how to accept the changes. In the video I posted I published the updates from the Assets file, but failed to accept the changes to the working file. Here was the fix for me:

"It appears that you did not accept the updates available on the subscribed file, indicated by the blue dot on the library icon on the top right corner:

Could you please click on this icon, go to the Updates tab, and accept all updates to the file?"

Yep experiencing the same problem… very patchy uptake of Published library updates in working files. Tried the ‘repair connection’ trick along with refresh/reboots

I am fighting this problem for years now. And reported this as a bug, but it is still not fixed.

I’ve found that Figma does not update instances with visibility turned off or nested within another hidden layer. This is the unfixed bug I’ve seen.

Sometimes the reason is that a to-be-updated component is nested within another component which contains outdated version. In that case Figma doesn’t update it as well. In this case rightfully.

I’ve found that Figma does not update instances with visibility turned off or nested within another hidden layer. This is the unfixed bug I’ve seen.

Could this bug also apply to components containing a hidden nested sub-component?

I have an instance of a component from a library containing text and a nested component (icon). The icon is hidden using a boolean property and the component will not update when I have made changes to it in the library.

Yes. Anything hidden is impacted by the bug.

FIXED for me. I was able to update changes from a library by clicking the open book icon in upper right corner of Figma. This icon also had a blue dot. It is the same feature as the previous text notification that there are changes to a library.

Hello community,

I have this issue: Update the library and publish changes. Then, I go to my file that’s using the library but I see not blue dot to update any changes. The weird thing is that if I search for the component in the list, it is updated! but the components that were already in the file (in the frames) are not…and that’s basically what I need… any idea? Thanks in advance, we’re currently losing a lot of time due to this broken workflow.

I resolved same issue. I had a boolean property that wasn’t used anymore by my component. In the library file, I selected my component and looked at the properties. The ! icon appeared next to a property that I didn’t use anymore.



After deleting that property and republishing, the component refreshed across my files correctly once more!

this truly saved my life! thank you so much!