I have encountered an issue which is quite annoying. Sometimes instances in the design disappear. It usually happens with nested components but the annoying thing is that it is hard to predict when and how that would happen which makes it hard to find a solution to address the problem.
As of today I have found, through some comments in the Figma forum, a temp solution which works arbitrarily: click on “Regenerate all instances (slow)” option in the cmd+k panel.
Is there something else that can be done?
Can Figma address the problem?
The big issue there is that collaborators/stakeholders who do not have edit permissions on the files cannot execute the action to regenerate instances so they see half empty frames and cannot do anything about this.
Hello there.
I have the same problem and every time I publish an update on the team’s library, the same nested components vanish in random files. It happens to my files too; I happen to maintain the libraries and also work on features so I know It’s not the font or different file configuration than mine.
Also this problem started happening around 3-4 months ago and I’m sure it had nothing to do with the nested components themselves. The usual suspects of this problem are simply defined and haven’t gotten a major update for a long time.
The solution, however, I’ve found to be useless updates on these nested component (i.e. changing the components’ name or adding a description.) and then publishing them. You might need to hard refresh or clear cache after the update. In some cases, the vanished will reappear but as it’s original form and all overrides are reset but I’ve seen the opposite too where the overrides remain intact after reappearance.
The “Regenerate all instances (slow)” never worked for me and I hope someday I can repair instance connections with the library.
Another thing I found to be strange in this case is when I help others go through with the solution I mentioned above, is that the problem seems to be fixed for me and not for them. I can see the component in it’s entirety but, on the same view when they’re following me in Figma, their components are corrupted and the same nested components are nowhere to be found. This case happened on a device with lower specs. Mine was a MacBook Pro (M3 Pro-18GB) and theirs was a MacBook Pro (M2-8GB). Maybe Figma’s having some problem with rendering nested instances in heavier files on devices with less memory available.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.