Components not updating correctly!

After a library swap, component instances did not update properly. Then I saw that variants didn’t appear (listed) under the component properties. My fix was to add a description to the ‘Component configuration’. It somehow refreshed the component.

I’m still having this issue a year later. I updated a button in the library file. I published the changes. I updated the library in my working file. I tried the following steps:

1. Reset instance to make sure it pulled all the changes. But it reset to the way it looked before I updated the library.
2. Deleted that instance, brought a new one in from “Assets”. Still looks like the old one.
3. Copied and pasted directly FROM THE LIBRARY FILE. IT MAGICALLY CHANGES TO THE OLD LOOK WTF

Hello, I have a design system file where components with variables are getting built as part of a tokenized library. I have published some of these tokenized components and have inserted instances of them in another file.

I then made changes to a component in the design system file. Specifically I refactored how components properties were organized for an avatar component. This same avatar component was being used in another file as an instance of the main component that got changes to its component properties. I then published the new improved avatar component from the design system file.

Then I went to the file that is consuming avatar instances from the design system library. I updated the file but the instances had a warning in their right side panel where their component properties are listed. The warning was saying that there is a missing variant and it provided a reset to default button. After clicking the reset to default button the avatar component finally updated to have the new component properties that mirror the changes that were made in the design system library component.

As a new user of Figma and publishing library components, this missing variant error message isn't very intuitive. The reset to default button also seems misleading and gives off the impression that the component will disregard the changes that were made to the published library component. Shouldn't the error message state that something changed in the main component and now this instance is out of sync with the changes made to the main component? Furthermore, why does the update modal window have an update all button if the instances aren't really all updated? Why does a user have to go to each instance of a component and click the reset to default button to finally make it update? Is there a force update to all instances even if a variant of the main component is missing?

Hey All, thanks for following up! 

As mentioned above, our support team usually needs to look at your files on a case by case basis to investigate this further. Again, please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new

Be sure to use your Figma account email, share a short video showing the issue you are seeing, include the links to your file and the library file, and share it with support-share@figma.com, so they can take a closer look.

Found out why it wasn’t updating in my instance. It was because there was an invalid property in my parent component. Once I removed that (it was a boolean that didn’t map to anything), I was then able to publish.

Check your parent component, and see if there are any ! symbols. Fix those and try again, that fixed it for me