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